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?
Thnks
"Bill Barker"
<[EMAIL PROTECTED]
.com> To
Sent by: news users@tomcat.apache.org
<[EMAIL PROTECTED] cc
rg>
No Phone Info Subject
Available Re: How to identify busy Tomcat
threads
08/02/2006 07:07
PM
Please respond to
"Tomcat Users
List"
<[EMAIL PROTECTED]
che.org>
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
.
>
> When i look at the Tomcat status page via the browser, if it tells me
that
> all the threads are busy - but the details of each of the connections
> indicates that these connections are in "k" - keep alive stage. Is there
> a
> way to tell using this status page or any other method if these Tomcat
> threads are actually being kept busy for keepalive purpose and not by
> requests coming in from the Apache webserver. I doubt that all the
Tomcat
> threads are busy doing useful work since on the Apache side the number
of
> active connections as seen using the server-status page is less than half
> the number of Tomcat threads that are busy.
>
For the AJP/1.3 Connector, The "k" stage means that Tomcat is waiting for
the next request to be forwarded from Apache.
> Thanks
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
