Thread pool settings

There are a variety of thread pools to configure. You use the administrative console to navigate to the page where you can configure threadpools.

To view this administrative console page, click Servers > Server Types > WebSphere application servers > server_name > Thread pools (Under Additional Properties), and select the thread pool that you need to configure. You can then observe the Name, Description, Minimum size, Maximum size, Thread inactivity timeout, and an option box to allow or not allow thread allocation beyond maximum thread size.

You use the administrative console to navigate to the appropriate page where you can configure the ORB Service thread pool.

ORB Service thread pools - To view this administrative console page, click Servers > Server Types > Application servers > server_name > Container services > ORB Service

After the Pass by reference check box, you can click Thread Pool Settings to make any thread pool adjustments for ORB service. Only the Minimum, Maximum, and Thread inactivity timeout are displayed.

The name of the thread pool to create. The name must be unique within the server.

This field is not displayed for the ORB service thread pool, when you clicked thread pool settings.

A text description of the thread pool.

This field is not displayed for the ORB service thread pool, when you clicked thread pool settings.

Specifies the minimum number of threads to allow in the thread pool. When an application server starts, no threads are initially assigned to the thread pool. Based on the workload, the application server adds threads to the thread pool until the number of threads in the pool equals the number that is specified in the Minimum size field. As the workload changes, threads are either added or removed. However, the number of threads in the thread pool IA always greater than the number that is specified in the Minimum size field, even if some of the threads are idle.

Specifies 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.

Specifies the number of milliseconds of inactivity that needs to 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.

Specifies whether the number of threads can increase beyond the maximum size that is 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 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. If set to true, the number of threads can increase beyond the maximum size configured for the thread pool.