Hi Philip Philip Wigg-2 wrote: > > jk-8300 - Max threads: 200 Current thread count: 200 Current thread > busy: 199 Max processing time: 1667835 ms Processing time: 20958.227 s > Request count: 131357 Error count: 586 Bytes received: 0.00 MB Bytes > sent: 11208.42 MB > > Stage Time B Sent B Recv Client VHost Request > K 5236624 ms ? ? 86.131.34.244 ? ? > K 4534173 ms ? ? 86.144.67.135 ? ? > K 4438805 ms ? ? 195.92.35.134 ? ? > K 4118296 ms ? ? 81.133.90.42 ? ? > K 3631710 ms ? ? 90.195.77.89 ? ? > K 4192041 ms ? ? 82.17.167.106 ? ? > [...] >
I'm having exactly the same issue than you. Our software stack is very similar: RHEL4 Java 1.5.0_14 mod_jk-1.2.20 tomcat5-5.5.23 Also, it happends only under heavy load scenarios, and not so often (a couple of times a month). It seems that at tomcat side, all threads are on keepalive status, while at mod_jk side, threads are on Busy status. So all stays this way forever, and no new requests are submited to tomcat. I've seen that AJP13 connections only can do keepalive when running with APR (apache portable runtime). Here are described the APR connector extensions: http://tomcat.apache.org/tomcat-5.5-doc/apr.html Currenly I'm doing tests with paramaters: firstReadTimeout,pollTime and pollerSize to control keepalive status. Philip, did you find a solution? ¿any one knows why with APR tomcat thread status is keepalive, socket connection is STABLISHED with mod_jk, but mod_jk believes thread is Busy? Thanks so much, Bernardo -- View this message in context: http://www.nabble.com/Tomcat-running-out-of-threads.-tp16812001p17270742.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
