> From: Martin Gainty [mailto:mgai...@hotmail.com] > Subject: RE: Running out of tomcat threads - why many threads in > RUNNABLEstage even with no activity
> http://publib.boulder.ibm.com/infocenter/wasinfo/v4r0/index.jsp?topic=/ > com.ibm.support.was40.doc/html/Plug_in/swg21163659.html Vaguely interesting, but not really applicable. The protocol in question here is AJP, not HTTP, and the connections are expected to be persistent, with no keep-alives needed. Unlike in the article cited, neither end will close the connection (unless an error occurs, of course). However, when there's an ill-behaved firewall in between Tomcat and the http server (as we appear to have here), keep-alives may be required. This FAQ entry looks promising: http://tomcat.apache.org/connectors-doc/miscellaneous/faq.html Look at the entry entitled "I've got a firewall between my web server and Tomcat which drops ajp13 connections after some time". Configuring keep-alives is a fairly low-overhead workaround, but it would be better to fix the firewall so it doesn't silently drop connections. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
