Thread pool settings
Use this page to configure a group of threads that an application server uses. Requests are sent to the server through any of the HTTP transport channels or HTTP transports. A thread pool enables components of the server to reuse threads to eliminate the need to create new threads at run time. Creating new threads expends time and resources.
To view this administrative console page, click...
Servers | Application Servers | servername | Thread Pools | thread pool
Configuration tab
- Name
The name of the thread pool to create. The name must be unique within the server.
Data type String - Description
A text description of the thread pool.
Data type String - Minimum size
Specifies the minimum number of threads to allow in the pool.
Data type Integer Default 10 - Maximum size
Specifies the maximum number of threads to allow in the pool.
If your Tivoli Performance Viewer shows the Percent Maxed metric to remain consistently in the double digits, consider increasing the Maximum size. The Percent Maxed metric indicates the amount of time that the configured threads are used. If there are several simultaneous clients connecting to the server-side ORB, increase the size to support up to 1000 clients.
Data type Integer Default 50 Recommended 50 (25 on Linux systems) - Thread inactivity timeout
Number of milliseconds of inactivity that should elapse before a thread is reclaimed. A value of 0 indicates not to wait and a negative value (less than 0) means to wait forever.
Note: The administrative console does not allow you to set the inactivity timeout to a negative number. To do this modify the value directly in the server.xml file.
Data type Integer Units Milliseconds Default 3500 - Allow thread allocation beyond maximum thread size
Specifies whether the number of threads can increase beyond the maximum size configured for the thread pool.
Data type Boolean Default Not enabled (false)
Tivoli is a trademark of the IBM Corporation in the United States, other countries, or both.