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://:8009/status/status and that has information like :
jk-8009 Max threads: 400 Min spare threads: 375 Max spare
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 w
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
thread
Had a couple of questions on Tomcat 5.0 behaviour on Linux
1. How would i interpret the "minSpareThreads" attribute in the AJP
connector element in server.xml? The document says that it is the number of
threads that Tomcat initially starts up with and also the minimum number of
idle threads that
I am using Apache with mod_jk 1.2.10(prefork MPM) running against Tomcat 5
within JBoss on Linux using JDK 1.4.2.07
Reading thru some of the postings within this Forum, it looks like we would
expect to see as many threads in tomcat as the number of MaxClients defined
in Apache.
In our setup, we ha
Rainer,
Thanks for your suggestion. I tried out the 1.2.18 version of
mod_jk(mod_jk-apache-2.0.46-linux-i686.so) but the behaviour seems to be
very similar. Here is some of the information that you asked for. For the
purpose of the test, i have only one Tomcat worker available. Though i had
on
Hello
I have an application which uses Apache(2.0.53) as the Webserver and
mod_jk(1.2.10) to forward servlet/jsp requests to Tomcat(5.0) as part of
the JBoss container - all running on Linux.
It looks like mod_jk is not reusing the existing connections that it
establishes with the Tomcat resulti
