I checked the whole thread, but I found no technical description of the problem observed. So apart from discussing the uses and stability of any do-not-reuse implementation, I would be interested in understanding the real problem, which started the discussion.
- What is known about the TCP behaviour of the firewall, i.e. what exactly has been observed with respect to TCP packets? - What are the platforms and versions of the used components on the Apache and the Tomcat side? W.r.t. the problem of shutting down a socket from the apache side and wasting tomcat threads, I never experienced a problem with that on *nix systems. I'll check again carefully, but I would be interested in any concrete information on which platforms and how such a problem can be reproduced. Regards, Rainer Jim Jagielski schrieb: > 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... 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... > > 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]
