You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/10/15 05:02:25 UTC

DO NOT REPLY [Bug 21763] - Tomcat 4.1.24 hangs under heavy load using http connector.

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=21763>.
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=21763

Tomcat 4.1.24 hangs under heavy load using http connector.

jswap@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From jswap@yahoo.com  2003-10-15 03:02 -------
I am running Tomcat v4.1.28 (which supposedly contains the fix to this bug, 
according to the previous comment), and am still getting this hanging 
problem.  I have tried configuring my connector two different ways, but get 
the hanging problem using both.  When I set the connector's maxProcessors to "-
1", during heavy load I see this in cataline.out:
"SEVERE: All threads are busy, waiting. Please increase maxThreads or check 
the servlet status200 200"

Once this error occurs, the server begins hanging and does not seem to recover 
until I restart tomcat.  A side note is that the number in the error message 
is 200.  This concerns me because I believe a value of -1 is supposed to 
mean "unlimited".  
I also tried setting the maxProcessors to 1000.  Under heavy load, I saw this 
error in catalina.out:
"SEVERE: All threads are busy, waiting. Please increase maxThreads or check 
the servlet status1000 1000"

Again, I had to restart Tomcat to recover from the hanging problem.

BTW, when I say "heavy load", I mean about 10 pages per second.  However, 
since we run on a dual Xeon, uptime reports a load of only about 0.5 so the 
CPU is definitely not the limiting factor.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org