RE: Tomcat running out of threads.

To: users@tomcat.apache.org Subject: RE: Tomcat running out of threads. 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

RE: Tomcat running out of threads.

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

RE: Tomcat running out of threads.

From: Bernardo Cabezas [mailto:ber...@bergantells.net] Hello, According to tomcat documentation, JkOptions +DisableReuse has some performance penalty, because opens new connection for each request. There is actually quite a lot of disagreement between the Tomcat committers about the

Re: Tomcat running out of threads.

hi.. i too have the same issue.. did anyone find solution? Bernardo Cabezas wrote: 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

RE: Tomcat running out of threads.

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

Re: Tomcat running out of threads.

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

Re: Tomcat running out of threads.

Philip Wigg schrieb: Hi, I have several Tomcat web applications that run in separate JVMs. I have one Apache instance that connects to the Tomcat instances via mod_jk. I am using:- RHEL ES 4.0 Java 1.5.0_14 mod_jk-1.2.25-httpd-2.0.59.so Tomcat 6.0.14. Usually the sites work fine and are very

Re: Tomcat running out of threads.

Thanks for your help. There should be at least one TP-Processor thread doing an accept on a socket. There is this one? TP-Processor4 daemon prio=1 tid=0x002b69b0e980 nid=0x655f runnable [0x41768000..0x41768ab0] at java.net.PlainSocketImpl.socketAccept(Native