4.2. General Diagnostics
- Verify the back end server is responsive by making a direct request to it.
- Monitor high load using one of the following methods:
- Twiddle
- Locate the appropriate
Twiddle
script for your environment (twiddle.sh
,twiddle.bat
ortwiddle.jar
) in the<JBOSS_HOME>/bin/
directory. - Run the following command:
<TWIDDLE> -u admin -p password get "jboss.web:name=ajp-127.0.0.1-8009,type=ThreadPool"
Use the script appropriate to your operating system and environment .Twiddle may need to be modified for each specific environment, but the above will work in a default JBoss instance where no ports have been changed and JBoss is starting on the localhost.
- JMX Console
- Navigate to
http://localhost:8080/jmx-console
. - Find the
jboss.web
section. - Click on
name=ajp-localhost/127.0.0.1-8009,type=ThreadPool
(or whichever AJPThreadPool
matches your environment) - Investigate the
currentThreadsBusy
attribute. If this attribute is reaching themaxThreads
there will be a problem as JBoss Web is reaching the definedThreadPool
capacity.