Mike Charnoky wrote: > > Is there a concise reference for this 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?
In my case, Tomcat hangs were caused by JVM problems and not related to Tomcat itself. This and badly behaved apps causing OOM conditions are probably the most common failure modes. The new code in the JK connectors allow mod_jk to "ping" Tomcat with a short timeout before sending a request there to determine if Tomcat is alive or not. This is useful when you have multiple Tomcats running, not quite as useful if you only have one Tomcat running but will keep Apache processes from waiting around forever for a response from a hung Tomcat. > 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? Last I heard, the next release of mod_jk will be worked on after the JK developers have released the next version of mod_jk2. This should happen in the next few weeks. It is a real solution, not a band-aid. -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
