Jim Jagielski wrote:
I and other have run into issues where the socket
between Apache and Tomcat (due to a in-between firewall)
isn't closed as it should be...
Yep, I have heared about things like that, on the Tomcat side the socket
seems opened but it closed on the httpd side.
The problem is that httpd will detect it and close the "closed" socket
but nothing reaches the TC... Until a timeout occurs on the TC side (OS
socket timeout).
New requests cause new connections to be opened that results in threads
increase (x2) in the TC with all the bad you could think of.
I'm digging further into
this as far as why the timeout isn't being honored, but
it got me thinking that a "no reuse" option might be
nice. Basically, it prevents reuse from ever being set
to TRUE...
Well the problem is how to detect that a "bad close" has happended.
Cheers
Jean-Frederic
PS: Also to be done with mod_proxy_ajp as well, but that's
a different list :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
