tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "André Vila Cova" <andremailingl...@gmail.com>
Subject Re: Tomcat - All threads (200) are currently busy
Date Fri, 13 Jul 2007 07:57:27 GMT
And it's possible to know what threads are really doing?
And I don't understand why having the following 3 connectors

maxThreads="400" minSpareThreads="25" maxSpareThreads="75"
 maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
 maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

I get error:
SEVERE: All threads (200) are currently busy, waiting. Increase maxThreads
(200) or check the servlet status.
Why 200? I dont have configured the value 200.

Thank you


On 7/12/07, Christopher Schultz <chris@christopherschultz.net> wrote:
>
> Ingo,
>
> Ingo Krabbe wrote:
> > Am Donnerstag, 12. Juli 2007 19:12 schrieb André Vila Cova:
> >> "http-8085-Processor24" daemon prio=1 tid=0x082f1378 nid=0x19c6 in
> >> Object.wait() [0xde118000..0xde118e20]
> >>         at java.lang.Object.wait(Native Method)
> >>         - waiting on <0xe619f748> (a
> >> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable)
> >
> > somehow this looks like a deadlock.
>
> I agree with Chuck: this is just an Object.wait() being called on the
> ControlRunnable object (which is probably the monitor for the thread
> pool). Most threads will be in this state. If you have threads in this
> state, then they are /not/ busy... they're waiting around for something
> to do!
>
> -chris
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message