Filter
Top Products
• Maximum size - Specifies the maximum number of threads to allow in the pool. This value should be set to
50% of the number of concurrent users planned for the LMS server.
Use the maximum thread size parameter to specify the maximum number of threads that can be pooled to handle
requests sent to the Web container. Requests are sent to the Web container through any of the HTTP transports. You
have two choices:
• Adjust the Minimum Size and Maximum Size for the thread pool.
• Turn on the Growable Thread Pool option to allow the thread pool to be increased by WAS as needed.
Although it is recommended that you select the Growable Pool Size option, if you decide to set the minimum and
maximum pool size, use these guidelines:
• The minimum size should be left to its default value of 10.
• The maximum size should be set to 100 and increased as necessary. You will know if the maximum pool size
needs to be increased if you observe the performance of the Learning or Delivery application servers. If you
notice that the response time is increasing while the CPU utilization of the machine is still low, this could be
a symptom of a starved system. The starvation could be caused by a bottleneck. A small thread pool size
could be one of the bottlenecks.
To view or change these parameters, use the following procedure:
• In the WebSphere Administrative Console, go to Application Servers - <server_name> - Web Container -
Thread Pool.
• View or adjust the Minimum Size, Maximum Size, and Growable thread pool to the desired size.
Adjusting the Web container MaxKeepAliveConnections
This parameter describes the maximum number of concurrent connections to the Web container that are allowed to
be kept alive, that is, to be processed in multiple requests. If this value is too small, performance is negatively
impacted.
To view or change this parameter, use the following procedure:
1. In the WebSphere Administrative Console, go to Application Servers - <server_name> - Web Container ->
HTTP Transports - <port_number> - Custom Properties.
2. Click New to create a new custom property and enter MaxKeepAliveConnections as Name.
3. Set the value to about 90 percent of the Maximum Size defined for the thread pool.
Adjusting the Web container MaxKeepAliveRequests parameter
This parameter describes the maximum number of requests allowed on a single keep-alive connection. This
parameter can help prevent denial of service attacks when a client tries to hold onto a keep-alive connection.
To view or change this parameter, use the following procedure:
1. In the WebSphere Administrative Console, go to Application Servers - <server_name> - Web Container -
HTTP Transports - <port_number> - Custom Properties.
2. Click New to create a new custom property and enter MaxKeepAliveRequests asName.
3. At the beginning, set the value to 100. If the application server requests are received from the WebSphere
plug-in only, increase this parameter's value.
Appendix A: LMS Performance and Fine-tuning Information 117