tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: How to identify busy Tomcat threads
Date Mon, 07 Aug 2006 16:42:59 GMT
Since this is an application in production, i cannot add in any
instrumentation to enable JConsole or JMX information. What i have
currently to work with is the Tomcat status at page
http://<server>:8009/status/status and that has information like :
jk-8009 Max threads: 400 Min spare threads: 375 Max spare threads: 375
Current thread count: 400 Current thread busy: 176

But looking at these stats, one cannot make out if the threads are actually
busy servicing requests or are they in keepalive state and the connection
between the Apache and Tomcat can be reused.

Would the JMX or JConsole give me a better picutre of the actual state of
each thread? I tried to look at the mod_jk trace logs on the Apache side
but could not decipher much to interpret if the Apache - Tomcat connections
are being reused.


             "Edmon Begoli"                                                
             m>                                                         To 
             No Phone Info             "Tomcat Users List"                 
             Available                 <>           
             08/03/2006 08:40                                      Subject 
             AM                        Re: How to identify busy Tomcat     
             Please respond to                                             
               "Tomcat Users                                               


The most precise way is to use JConsole or other JMX client and to lookup
the maxThreads and
related properties of the 8009 jk connector.


---------- Forwarded message ----------
To: "Tomcat Users List" <>
Date: Thu, 3 Aug 2006 00:14:19 -0700
Subject: Re: How to identify busy Tomcat threads
Thanks for that tip. Since the current Tomcat status page shows these
threads as busy even though they are waiting for connections from Apache,
it is a bit misleading since we are not sure if we are out of capacity on
the Tomcat side and if we need to increase to Tomcat capacity.
What is the best way to judge if we are running out of Tomcat resources?


Thank you,
Edmon Begoli

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message