WAS v8.5 > Reference > Sets
Thread pool settings page
Use this page to configure a thread pool that an application server uses. A thread pool enables components of the server to reuse threads, which eliminates the need to create new threads at run time. Creating new threads expends time and resources.
To view this dmgr console page, click Servers > Server Types > WebSphere application servers > server_name > Thread pools, and select the thread pool that you need to configure.
To configure the thread pool for the ORB Service, click Servers > Server Types > WebSphere application servers > server_name > Container services > ORB service. Under Thread Pool Settings, select one of the following actions:
- Select Use the ORB.thread.pool settings associated with the Thread Pool Manager, and then click ORB thread pool settings, or
- Select Use the thread pool settings directly associated with the ORB service, and then click Thread pool settings.
Because these dmgr console panels display information dynamically, you might not see all of the fields listed on any particular panel.
Name
The name of the thread pool to create. The name must be unique within the server.
This field is not displayed if you click thread pool settings.
| Information | Value |
|---|---|
| Data type | String |
A text description of the thread pool.
This field is not displayed if you click thread pool settings.
| Information | Value |
|---|---|
| Data type | String |
Minimum size
Minimum number of threads to allow in the pool. When an application server starts, no threads are initially assigned to the thread pool. Threads are added to the thread pool as the workload assigned to the application server requires them, until the number of threads in the pool equals the number specified in the Minimum size field. After this point in time, additional threads are added and removed as the workload changes. However, the number of threads in the pool never decreases beneath the number specified in the Minimum size field, even if some of the threads are idle.
This field is not displayed if you click thread pool settings.
| Information | Value |
|---|---|
| Data type | Integer |
| Default | 50 |
Maximum size
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 the configured threads are used.
| Information | Value |
|---|---|
| Data type | Integer |
| Default | 50 |
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.
The dmgr console does not allow you to set the inactivity timeout to a negative number. To do this modify the value directly in server.xml.
| Information | Value |
|---|---|
| Data type | Integer |
| Units | Milliseconds |
| Default | 60000 |
For transitioning users: The default value was changed in version 8.0
from 35000 milliseconds as documented in version 6.0 to the correct default of 60000 milliseconds.trns
Allow thread allocation beyond maximum thread size
Whether the number of threads can increase beyond the maximum size that is configured for the thread pool.
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 thread pool that is allowed to grow expands beyond the maximum size, the additional threads are not reused and are discarded from the pool after required work items are completed.
| Information | Value |
|---|---|
| Data type | Boolean |
| Default | Cleared |
Related
Tune the application serving environment
Related information:
TCP transport channel settings