Hi! I've this two processes:
tomcat 6404 0.0 2.6 484396 105456 ? Sl 01:05 0:14 /usr/local/java1.5/bin/java -Xms64m -Xmx200m -Xss512k - Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager - Djava.util.logging.conf tomcat 6555 0.1 3.8 516420 154452 ? Sl 01:09 0:39 /usr/local/java1.5/bin/java -Xms64m -Xmx200m -Xss512k - Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager - Djava.util.logging.conf Output is null when I execute the following command: [EMAIL PROTECTED] ~]# kill -QUIT 6404 [EMAIL PROTECTED] ~]# How can I see what thread is doing? Thank You On 7/11/07, Titi Wangsa <[EMAIL PROTECTED]> wrote:
probably some threads are performing database operation and it takes too long so new threads are being spawned, the new threads are also taking too long, so newer threads are being spawned. too much spawning, that is what is causing the limit break. On 7/12/07, André Vila Cova <[EMAIL PROTECTED]> wrote: > I don't think so... I will see..but, why i get the error? > SEVERE: All threads (200) are currently *busy*, waiting. *Increase > > > On 7/11/07, Mladen Turk <[EMAIL PROTECTED]> wrote: > > > > André Vila Cova wrote: > > > Hello! > > > > > > I get lot of times the following error: > > > > > > SEVERE: All threads (200) are currently *busy*, waiting. *Increase > > > maxThreads* > > > ** > > > *Strange is that i've configured in server.xml the following > > > (maxThreads=400):* > > > * > > > > > > > You have probably done that for a wrong connector. > > > > Regards, > > Mladen. > > > > --------------------------------------------------------------------- > > To start a new topic, e-mail: users@tomcat.apache.org > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
