| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Active_threads |
Indicates the total number of active threads in this pool. |
Number |
A high value for this measure is indicative of a high load on the applications deployed on the WebLogic server. 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.
|
| Total_thread_count |
Indicates the total number of threads in this pool. |
Number |
|
| Idle_thread_count |
Indicates the number of idle threads (i.e., the threads that are ready to process a new job as and when it arrives) in the pool. |
Number |
|
| Hogging_thread_count |
Indicates the number of threads that are currently hogged by a request. |
Number |
Ideally, the value of this measure should be low. These threads will either be declared as stuck after the configured timeout or will return to the pool before that. The self-tuning mechanism will backfill if necessary. WebLogic Server automatically detects when a thread in an execute queue becomes “stuck”. Because a stuck thread cannot complete its current work or accept new work, the server logs a message each time it diagnoses a stuck thread.
WebLogic Server diagnoses a thread as stuck if it is continually working (not idle) for a set period of time. You can tune a server's thread detection behavior by changing the length of time before a thread is diagnosed as stuck, and by changing the frequency with which the server checks for stuck threads. Although you can change the criteria WebLogic Server uses to determine whether a thread is stuck, you cannot change the default behavior of setting the “warning” and “critical” health states when all threads in a particular execute queue become stuck. |
| Standby_thread_count |
Indicates the number of threads that are currently in the standby pool. |
Number |
Threads that are not needed to handle the present work load are designated as standby and are added to the standby pool. These threads are activated when more threads are needed. |
| Queue_length |
Indicates the number of pending requests in the priority queue. |
Number |
This measure comprises of both the internal system requests and requests made by the user. A low value is desired for this measure. A high value or a sudden increase in this value may indicate a sudden slowdown in responsiveness or a performance bottleneck. |
| Throughput |
Indicates the number of requests in the priority queue that are completed. |
Number |
|