Yup.... that's what I thought was happening. When all threads are busy,
tomcat can't accept any more requests. To an extent tomcat still
accepts some request and waits for a thread to free up but eventually
it'll reject the requests with a 50x error.
Either the tomcat service is legitimately overloaded (over 250
concurrent requests) or a design issue is preventing threads from being
freed for new requests. You'll have to do some profiling to determine
which it is and the best way to fix it. Also see Chuck Caldarale's
message regarding potential causes to look for.
--David
Etienne Lacombe wrote:
David,
I followed your advice and killed the JVM so as to get the stack trace when it
stopped responding this afternoon.
Here is what we had in the log before the stack trace:
3:27 org.apache....ThreadPool logFull
All threads (250) are currently busy, waiting. Increase maxThreads (250) or
check the servlet status.
3:27 to 3:41 A few log statements from our webapps
3:41 - the stack trace dump... All threads are either TIMED_WAITING, RUNNABLE
or WAITING.
Etienne
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
