Kurt Overberg wrote:
It seems that the number of connections between the apache and the tomcats just start escalating for some reason. mod_jk.log shows a ton (>50) of these errors:
Hard to tell without httpd.conf and server.xml. Two things you should know: 1. MaxClients shuld be <= maxThreads 2. If you have MaxRequestsPerChild != 0 you must set connectionTimeout in server.xml If you have connectionTimeout in server.xml add connect_timeout=60000 and prepost_timeout=60000 to each worker (except loadbalancer). Also if you have a firewall between Apache Httpd and Tomcat use connect_timeout and prepost_timeout because the firewall can cut the inactive connections. Also add connectionTimeout that will reflect the firewall cut time. Anyhow AJP13 protocol is persistent, so if any part can close the socket (simple restart) the other one will not know about that, the socket will be half-closed and the connection count will rise until one part breaks down (usually Tomcat). To deal with that issues add connectionTimeout="600000" (10 minutes) to server.xml and ... worker.xxx.connect_timeout=60000 (1 minute) worker.xxx.prepost_timeout=60000 (1 minute) The later will force so called PING/PONG packets to be send between web server and Tomcat. If the response packet is not received within the specified time the socket will be closed and the new one will be created. Regards, Mladen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
