This is in regards to this error message which kills tomcat:
SEVERE: All threads are busy, waiting. Please increase maxThreads or
check the servlet status75 75"
Erik: How do you know this is fixed in 4.1.29?
Also, would increasing maxProcesses help in the connector?
Travis
On Tuesday, Novemb
Yoav,
Howdy,
At least on unix, it's a QUIT (not STOP) signal.
kill -s QUIT processId
Oh! Brain fart. Yep, it's QUIT, not STOP. It's still CTRL-\ from the
terminal.
-chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additiona
ember 05, 2003 8:27 AM
>To: Tomcat Users List
>Subject: [OT] How to get a thread dump (was: Severe notification ...)
>
>Mufaddal,
> > Is
>> there a facility in tomcat that would allow me to dump its threads
and
>> allow me to see where the threads are waiting and not mo
Mufaddal,
> Is
there a facility in tomcat that would allow me to dump its threads and
allow me to see where the threads are waiting and not moving on ?
People need to stop asking this question and do "google java virtual
machine thread dump". Sheesh...
Send the process a STOP signal, and it will
From java.sun.com:
To get a full thread dump of a running Java application, send a
|SIGQUIT| signal to the JVM process. This can be done from command line
as |kill -QUIT .
I think if you're running the jvm in a console you can do something like
CTRL-\ or something... Also, there is some option
Hi,
I am facing this problem in 4.1.18. I havent tried to upgrade yet, but
would like to know if there is a way in Tomcat to get a dump of my
tomcat threads and see where the bottleneck is. How do I do this ? Is
there a facility in tomcat that would allow me to dump its threads and
allow me to
Hi,
I have had this problem exactly, and have been told that it is a bug in
4.1.24 to 4.1.27 that has been fixed in 4.1.29. Essentially, when
working at or near the maximum connections (as defined in the Connector
config in server.xml) some threads get permanently deadlocked or
something. I di
I have my webapp up and running and am stress testing it. After a while
I get this:
"Nov 4, 2003 1:50:12 PM org.apache.tomcat.util.threads.ThreadPool
logFull
SEVERE: All threads are busy, waiting. Please increase maxThreads or
check the servlet status75 75"
I have no idea why all threads would
