I know this sounds very general, but 1.2.10 is quite antique. First update to 1.2.18, try again and if your problem is still reproducible, post your config (workers.properties and Jk* from httpd.conf) and relevant parts of the mod_jk-Logfile with LogLevel trace.
Also try to relate tcp connection information from netstat using you AJP port to your thread observations. Regards, Rainer [EMAIL PROTECTED] schrieb: > Hello > > I have an application which uses Apache(2.0.53) as the Webserver and > mod_jk(1.2.10) to forward servlet/jsp requests to Tomcat(5.0) as part of > the JBoss container - all running on Linux. > It looks like mod_jk is not reusing the existing connections that it > establishes with the Tomcat resulting in a large number of Tomcat threads > which are in KeepAlive state as reported by the Tomcat console. > I do not have any timeouts set either on the Apache side or Tomcat side of > the connector. > The JBoss/Tomcat 5.0 document states that the default connectionTimeout > within the AJP 1.3 connector on the Tomcat side is 60 seconds but it does > not seem to be the case. > > I am trying to force this connectionTimeout to clean up the large number of > Tomcat threads, but i am not sure if this is the best thing to do. > Is there anything on the Apache side in the workers.properties that i could > specify to make sure mod_jk reuses these connections. > > Thanks > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
