Hello, According to tomcat documentation, JkOptions +DisableReuse has some performance penalty, because opens new connection for each request.
In my case, issue was solved by setting the param: connectionTimeout on the ajp13 <connector /> entry on tomcat's server.xml Also look at docs for firstReadTimeout parameter. Now mod_jk is using a pool of connectors, but tomcat expires old threads on the pool so issue was solved. Regards, Bernardo. Mark Thomas-18 wrote: > >> From: Hari Prasad [mailto:ursha...@yahoo.co.in] >> >> hi.. i too have the same issue.. >> did anyone find solution? > > 1. JkOptions +DisableReuse > 2. Use correct timeouts and CPing/CPong > > I'd go with option 1. YMMV. > > Mark > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://www.nabble.com/Tomcat-running-out-of-threads.-tp16812001p21413171.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