DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799
Tomcat dies after being up for a while (complains about maxThreads)
------- Additional Comments From andy@xadra.com 2003-07-24 11:50 -------
We are seeing this same issue as well with 4.1.24 and 5.0.4alpha. We have a
load test program that sends a high volume of concurrent requests to Tomcat
and it consistenly refuses connections at around the 75th connection attempt.
After a bit, it begins accepting connections again.
We have verified that both minProcessors and maxProcessors really seem to have
no effect. If you set minProcessors to say 50 or 100 and then perform a thread
dump, you will see that there are not 50 pre-allocated threads. If you set
maxProcessors to say 1000, you will still see failures around the 75
connection. It's also unclear why the acceptCount is limited to 128 pending
connections.
We have generated thread dumps and there are no deadlocks. All available
threads are currently processing valid requests. The pool is simply out of
threads and.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
|