Jim Jagielski wrote:
Jean-frederic Clere wrote:
Rainer Jung wrote:
Jim Jagielski schrieb:
I would call this a broken firewall, right?
Yep, but that happends ,-(
I think I have seen a case where the connection Apache-FW was closed
correctly and the FW-Tomcat just "forgotten".
I don't know exactly what happends the only thing I have seen is that
the TC thread stays in the Socket.read() for about 7 minutes and during
those 7 minutes httpd creates new connections until TC gets out of threads.
Yeah, once it happens, you quickly fall off the cliff.
With the increasing number of environs that are shoving a firewall
between Apache and Tomcat, I've been seeing this more and more
often. Disabling reuse does address the problem;
Well that is a last chance option. The socket has to be reopened the
whole stuff will be very slow... (What happends with keep-alive...).
Won't |recover_time be more helpfull for that case?|
the other "fixes"
involve either crippling Apache (setting MaxRequestsPerChild to 1!)
That adds a fork() to the close/open.
or dropping AJP all together.
That isn't a mod_jk feature ;-)
Cheers
Jean-Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
