70. Middle Tier - Threads
The number of threads is limited in every Managed Server. Many threads that
are defined as stuck may result in slow system response. This check will
monitor if stuck threads exist.
Multiple Instances: Yes (per managed server)
Interval: Every 5 minutes (288 times per day)
| Status |
Expression |
| Critical |
If (number of Stuck Threads > 10)
| Impact |
Many Stuck Threads in the Managed Server. Slow system
responsiveness. A stuck thread is a thread that has been active
longer than the stuck thread timeout limit configured in the
Application Server (default: 600 seconds). |
| Suggestion |
Look in thread dump for further information about the
problem. Configuration is done in IFS Middleware Server. |
|
| Warning |
If (number of Stuck Threads > 0)
| Impact |
Stuck Threads in the Managed Server. Slow system
responsiveness. A stuck thread is a thread that has been active
longer than the stuck thread timeout limit configured in the
Application Server (default: 600 seconds). |
| Suggestion |
Look in thread dump for further information about the
problem. Configuration is done in IFS Middleware Server. |
|
| OK |
If not status Warning or Critical. |
| Unknown |
Missing application response. |
| Metric & Service |
Command line example |
| Stuck Threads |
java -jar application-monitoring-metrics-cli.jar mws -host=localhost
-server=<Managed Server Name> -port=<Managed Server JMX Port>
-user=ifsmon -pass=<password> -request=stuck_threads -wa=0 -ca=10 |