WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

Messaging connection pool
When using the messaging service make sure that you configured the
messaging pool according to your needs. Depending on which messaging
service you use and how messaging is used in the application you have different
pooling options. Pools for message processing can, for example, be configured
on a per connection factory basis. The messaging listener service provides a
separate pool that can be configured through the Integrated Solutions Console.
To do so, navigate to Servers → Application Servers → →
Messaging → Message Listener Service.
Further pooling options exist when using activation specifications to invoke
message driven beans (MDBs).
Mediation thread pool
If you want to run multiple mediations in your service integration bus
infrastructure concurrently, you need to configure a mediation thread pool using
the wsadmin command line interface.
Database connection pool
The database connection pool is another common location for bottlenecks,
especially in data-driven applications. The default pool size is 10, and depending
on the nature of the application and the number of requests, the default setting
might not be sufficient. During implementation testing, pay special attention to
the pool usage and adjust the pool size accordingly. The connections in the pool
consume additional Java heap, so you might be required to go back and adjust
the heap size after tuning the pool size.
Web services connection pool
Use HTTP transport properties for Java API for XML-based Web Services
(JAX-WS) and Java API for XML-based RPC (JAX-RPC) Web services to
manage the connection pool for HTTP outbound connections. Configure the
content encoding of the HTTP message, enable HTTP persistent connection,
and resent the HTTP request when a time-out occurs.
7.3.4 Application tuning
Tuning your application is the most important part of your tuning activities. While
environment-related tuning is important to optimize resource use and avoid
bottlenecks, it cannot compensate for a poorly written application. The majority of
performance-related problems are related to application design and coding
techniques. Only a well-designed application, implemented with the best
practices for programming, will give you good throughput and response times.
240 WebSphere Application Server V7.0: Concepts, Planning, and Design