> > [Pantvaidya, Vishwajit] Here are figures from 3 of the servers which
> have
> > not yet run out of threads (so the thread count does not add up to 200).
> I
> > have taken these late at night when no users are present, so I was
> > expecting all threads to be Waiting for tomcat thread-pool.
> >
> > 1. Total TP-Processor threads 48, Waiting 46, Runnable 2
> > 2. Total TP-Processor threads 40, Waiting 29, Runnable 11
> > 3. Total TP-Processor threads 120, Waiting 7, Runnable 113
> >
> >
[Pantvaidya, Vishwajit] Since Rainer mentioned that he would like to see more
of the stack trace, here are the complete stack traces for a Runnable and
Waiting thread from #3 above. All Runnable/Waiting threads from all the above
cases have same stack trace as below:
"TP-Processor119" - Thread t...@2294
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:607)
at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:545)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:672)
at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
"TP-Processor118" - Thread t...@2293
java.lang.Thread.State: WAITING on
org.apache.tomcat.util.threads.threadpool$controlrunna...@3579cafe
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:474)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:656)
at java.lang.Thread.run(Thread.java:595)
