On 08/11/2007, at 4:51 PM, Jim Cox wrote:
On Nov 8, 2007 10:41 AM, <[EMAIL PROTECTED]> wrote:In resolving our current bottleneck i used JProfiler to see what thetomcat applications were doing and when under high load there are a lot ofthreads which are blocked on this:org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run()This suggests that they are spending all their time waiting for tomcat torun them, either way they're not runnable anyway."http80-Processor131" daemon prio=5 tid=0x00baa7c0 nid=0x10f9 in Object.wait() [0xa5e81000..0xa5e819c8] at java.lang.Object.wait(Native Method) - waiting on <0xc9d99d20> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) FWIW, I always interpreted those as HTTP servicing threads waiting for something to do (i.e. not a bad thing at all).
Have you tried running your profiler against a tomcat not doing ANY requests?
I agree with Jim on this one - These are threads WAITING on a connection...
and not doing anything.Have a look in tomcat manager, and then you can see how many 'free' connections
you have. Cheers Andrew
smime.p7s
Description: S/MIME cryptographic signature