4:02] [info] "VM Periodic Task Thread"
[2007-01-30 12:24:02] [info] prio=10 tid=0x00a99930
[2007-01-30 12:24:02] [info] nid=0xab4
[2007-01-30 12:24:02] [info] waiting on condition
[2007-01-30 12:24:02] [info]
[2007-01-30 12:24:02] [info]
--
View this message in context:
htt
The thread dump basically tells us, that your tomcat is idle. Nothing is
in progress there. This is in contrast to mod_jk having problems to
connect to tomcat.
I can see from your thread dump, that you are using the native apr
connector. Since we had a couple of bug fix releases for apr, it wo
x00344be8
[2007-01-29 17:21:07] [info] nid=0x1030
[2007-01-29 17:21:07] [info] runnable
[2007-01-29 17:21:07] [info] [0x0000..0x0006f5bc]
[2007-01-29 17:21:07] [info]
[2007-01-29 17:21:07] [info] "VM Thread"
[2007-01-29 1
I had a look at your log files. It really looks like something is wrong
on the remote=tomcat side (or in between mod_jk and tomcat). Please do a
couple of thread dumps for the tomcat JVM immediately after your stress
test, during the time you cannot send request via mod_jk.
Under Windows you h
ation attempt=2
[Wed Jan 24 13:02:56 2007] [0284:3868] [error] jk_ajp_common.c (1928):
(ajp13) Connecting to tomcat failed. Tomcat is probably not started or is
listening on the wrong port
[Wed Jan 24 13:02:56 2007] [0284:3868] [debug] jk_ajp_common.c (2258):
recycling connection pool slot=40 for wor
