tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony J. Biacco" <>
Subject RE: mod_jk pool/thread/configure questions
Date Thu, 19 Feb 2009 18:17:08 GMT
Thanx for all that. Responses below.

>> the max of 400 and stay there until tomcat is restarted. Is there a
>> to resolve this? And more importantly, should I resolve it? Is there
>> major memory/CPU inplications to it keeping its  threads at the max?

>Do a thread dump "kill -QUIT". It goes to catalina.out and will tell 
>you, what all those 400 threads are doing. Maybe they are stuck working

>on old requests nobody is waiting for.

All the idle threads look like this:

"ajp-8009-63" daemon prio=10 tid=0x000000001b52f000 nid=0x52ec in
Object.wait() [0x000000004610c000..0x000000004610cd90]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00002b3aebf5f840> (a$Worker)
        at java.lang.Object.wait(
        - locked <0x00002b3aebf5f840> (a$Worker)

>> worker.template.reply_timeout=20000

>When using such an ambitious reply_timeout, also use

I'm under the understanding this is the timeout between packet responses
from tomcat. I don't think they should be any longer than this.

> worker.template.socket_connect_timeout=5000
> worker.template.ping_mode=A
> worker.template.ping_timeout=25000

Yeah, I tried 5 and 10, but jk was reporting it not getting cpongs back
from tomcat.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message