I can try tuning this on the servers. But as I told in my first email, this wierd problem started happening only after migrating to Tomcat 5.5. So if these were to create a problem, I should have faced it in 4.0.6 also - Right.
..Raj On Thu, 08 Dec 2005 Mladen Turk wrote : >Raja Neravati wrote: >>worker.worker1.recycle_timeout=60 > >Remove this directive. > >>worker.worker1.retries=3 >> >> >><Connector port="8009" enableLookups="false" protocol="AJP/1.3" >>minSpareThreads="100" maxThreads="300" maxSpareThreads="80" acceptCount="60" >>debug="0" connectionTimeout="-1" /> > >maxThreads should be equal to MaxClients in httpd.conf. If it's smaller >then set connectionTimeout="60000" and add: > >worker.worker1.connect_timeout=60000 >worker.worker1.prepost_timeout=60000 > >The later would be recomended if you have firewall between mod_jk >and Tomcat. > >And of course, use the latest stable mod_jk (1.2.15) >If you look at the: >http://tomcat.apache.org/connectors-doc/changelog.html >You will see that couple of things were fixed since 1.2.10 :) > >Regards, >Mladen. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >
