Thread pool settings: WAS v5.1

Thread pool settings

To configure a group of threads for an appserver...
Administrative Console | Servers | Manage Application Servers | server | ORB Service | Thread Pool

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.

Configuration tab

Minimum size Specifies the minimum number of threads to allow in the pool.

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.
Recommended value is 50 (25 on Linux systems)

Thread inactivity timeout Specifies 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 that 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 config.xml file.
Default is 3500

Is Growable Specifies whether the number of threads can increase beyond the maximum size configured for the thread pool.
Valid values are Allow thread allocation beyond maximum thread size or Not enabled.

Minimum size	Specifies the minimum number of threads to allow in the pool.
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. Recommended value is 50 (25 on Linux systems)
Thread inactivity timeout	Specifies 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 that 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 config.xml file. Default is 3500
Is Growable	Specifies whether the number of threads can increase beyond the maximum size configured for the thread pool. Valid values are Allow thread allocation beyond maximum thread size or Not enabled.