Here is the continuation of the thread dump:
[2007-01-30 12:24:02] [info]at java.lang.Object.wait(Unknown Source)
[2007-01-30 12:24:02] [info]at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656)
[2007-01-30 12:24:02] [info]- locked <0x09516170> (a
org.
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
We'll repeat the stresstest with subsequent threaddump tomorrow morning.
However, I just experienced the same TCP Connections aborted scenario on
another test server running the same web service ('/demo-e/servlet'), and I
managed to get a threaddump from there:
[2007-01-29 17:21:07] [info] Consol
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
