tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 5735] - HTTP connector running out of processors under heavy load
Date Tue, 19 Feb 2002 04:42:09 GMT
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=5735>.
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=5735

HTTP connector running out of processors under heavy load





------- Additional Comments From glenn@apache.org  2002-02-19 04:42 -------
I think we are getting close to identifying how this bug behaves.

Everytime you get the following Exception:

java.io.IOException: Broken pipe
        at java.net.SocketOutputStream.socketWrite(Native Method)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:96)
        at org.apache.ajp.Ajp13.send(Ajp13.java:525)
        at org.apache.ajp.RequestHandler.finish(RequestHandler.java:496)
        at org.apache.ajp.Ajp13.finish(Ajp13.java:395)
        at
org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:192)
        at
org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:453)
        at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:540)
        at java.lang.Thread.run(Thread.java:484)

Ajp13Connection spawns a new Ajp13Processor, if you have reached maxProccessors,
a connection is rejected.

In a long test run I am doing I see this maybe once an hour.
A bunch of the above exceptions, with an identical number of attempts
to spawn a new Ajp13Processor.

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


Mime
View raw message