Ok.. adding some info to mod jk logs and doing some thread and heap dumps, I figured that, during peak traffic hours, the garbage collection gets more frequest and takes longer. This slows down the overall system and the threads start piling up. Requests that used to take 2 seconds now take a couple of hundred seconds. The application isn't using the swap space though. It takes a long as 15 minutes for the system to recover completely and sometimes I have to restart.
Now how can I intelligently use the timeout settings to kill the long running requests and prevent threads from making it worse? In httpd.conf, I have: Timeout 120 In worker.properties, I have: worker.node1.connection_pool_timeout=600 In the tomcat AJP connector, I have: connectionTimeout="600000" How can I ensure that no request is taking longer than 3 minutes? -- View this message in context: http://www.nabble.com/Apache%2C-Tomcat%2C-Mod_JK-Configurations-tp23751902p23817845.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
