On 20.05.2009 19:47, Caldarale, Charles R wrote: >> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] >> Subject: RE: Running out of tomcat threads - why many threads >> inRUNNABLEstage even with no activity >> >>>> - Setting connectionTimeout in server.xml seems to have resolved >>>> the issue >> Only because you're throwing away what appears to be a usable >> connection that's designed to be persistent. > > Do you have something between Tomcat and httpd that could be silently closing > connections? (Some badly behaved firewalls are known to do this.) That > would make the existing AJP connections useless, without notifying the Tomcat > threads that the connection is no longer there. Setting the timeout would > allow those connections to be discarded and new ones created.
That's a good point. You should check both sides by using "netstat -an". The Apache side and the Tomcat side (without connectionTimeout, so you can see the problem in the original form). See whether the number of AJP connections in the various TCP states differs much between the netstat output on the Apache and on the Tomcat system. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
