* Tomcat 4.1.24-LE * Apache 1.3.27 * mod_jk 1.2.4 * Sun JVM 1.4.1_05 * all running on Linux RH 8.0
For quite some time now, our website has been encountering a "hung tomcat problem" at random times. The symptoms are typically:
* Apache "server status" scoreboard shows a max number of connections in the
"W" state (waiting for reply).
* "top" shows one tomcat process (thread) is using 99.9% of CPU and in
"S" state (sleeping)
* Tomcat takes forever to service connections, but it is still running
* Even after the server is taken offline and the number of apache connections
has dropped to 0, tomcat is still sluggish and still has one thread that
is hogging CPU
Apparently, this seems to be a common problem based on some googling and digging through the archives. Particularly noteworthy are some new mod_jk additions that will debut in mod_jk 1.2.6. The Tomcat "Workers HowTo" document (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk/workershowto.html) lists several parameters that have been added specifically to deal with a "hung tomcat" problem (eg: connect_timeout, prepost_timeout, reply_timeout, recover_options).
This leads me a a few questions: What exactly is the nature of this "hung tomcat" problem? It is intrinsically a tomcat issue or is it a problem with a badly behaved app? How can I determine what is causing the hang? Is there something in the archives that I am completely missing?
Also: Any news on when mod_jk 1.2.6 will be available? Are the new config parameters merely a band-aid or a real solution?
Thanks!
Mike C
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
