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 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 > Manage Application Servers > server_name > ORB Service > Thread Pool. (You can reach this page through more than one navigational route.)
Configuration tab
Data type | Integer |
Default | 10 |
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.
Data type | Integer |
Default | 50 |
Recommended | 50 (25 on Linux systems) |
Note: The administrative console does not allow you to set the inactivity timeout to a negative number. To do this you must modify the value directly in the server.xml file.
Data type | Integer |
Units | Milliseconds |
Default | 3500 |
When a growable thread pool expands beyond the maximum size, the additional threads will not be reused and will be discarded from the pool after processing of the work items for which they were created is completed. When additional threads are created, a message is logged in the SYSOUT file to let you know that you went beyond the maximum size set for the thread pool.
Data type | Boolean |
Default | Not enabled (false) |
Range | Valid values are Allow thread allocation beyond maximum thread size or Not enabled. |