eG Help

To optimize performance and at the same time to support concurrent accesses from users, the application server uses thread pools. It is critical to monitor a WebSphere server's thread pools on an ongoing basis. This test monitors the thread pools on a WebSphere server.

Outputs of the test : One set of results for each thread on the WebSphere application server

Measurement	Description	Measurement Unit	Interpretation
Active_count	Indicates the number of threads that are currently active.	Number	Indicates the number of threads that are currently active. This measure is also useful for determining usage trends. For example, it can show the time of day and the day of the week in which you usually reach peak thread count. In addition, the creation of too many threads can result in out of memory errors or thrashing. By watching this metric, you can reduce excessive memory consumption before it's too late.
Create_count	Indicates the number of threads that were created since the last measurement period.	Number	A sudden increase in the value of this measure directly relates to an increase in the activity happening in this application.
Destroy_count	Indicates the number of threads that were destroyed since the last measurement period.	Number	A decrease in the value of this measure indicates that the threads are being active for a long period of time, which might indicate anomalies within the application.
Pool_size	Indicates the number of threads in the pool, currently.	Number	If the pool size is high and the number of active threads is low, it signifies that the threads are not being destroyed immediately after use.
Threads_hung_count	Indicates the number of concurrently stopped threads.	Number
Percent_used	Indicates the percent usage of threads in the pool.	Percent	The value of this measure is computed as a on the basis of the total number of threads configured in the pool, and not the pool size.