Use this page to configure a group of threads that an application server uses. 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, you can choose more than one navigational route. For example, click Servers > Application Servers > server_name > Container Services > ORB Service > Thread Pool, then select the thread pool.
Note: Because these console panels display information dynamically, you might not see all of the fields listed on any particular panel.
Configuration tab
The name of the thread pool to create. The name must be unique within the server.
| Data type | String |
A text description of the thread pool.
| Data type | String |
The minimum number of threads to allow in the pool.
| Data type | Integer |
| Default | 10 |
The maximum number of threads to maintain in the default thread 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.
| Data type | Integer |
| Default | 50 |
| Recommended | 50 (25 on Linux systems) |
The 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 |
Whether the number of threads can increase beyond the maximum size configured for the thread pool.
The maximum number of threads that can be created is constrained only within the limits of the Java Virtual Machine and the operating system. When a growable thread pool expands beyond the maximum size, the additional threads are not reused and are 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) |
Related tasks
Tuning the application serving environment
Related information
TCP transport channel settings