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 2002/01/28 16:53:19 UTC

DO NOT REPLY [Bug 6068] New: - AJP13 "bad read", IOException

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

AJP13 "bad read", IOException

           Summary: AJP13 "bad read", IOException
           Product: Tomcat 4
           Version: 4.0 Final
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: AJP Connector
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: nick@digivis.com


There are many AJP13 errors in my catalina.out:

[Ajp13] bad read: -103
Ajp13Processor[8011][2] process:  done

(repeated many, many times)

and

java.io.IOException: Broken pipe
        at java.net.SocketOutputStream.socketWrite(Native Method)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
        at org.apache.ajp.Ajp13.send(Ajp13.java:966)
        at org.apache.ajp.Ajp13.finish(Ajp13.java:815)
        at
org.apache.ajp.tomcat4.Ajp13Response.finishResponse(Ajp13Response.java:192)
        at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:373)
        at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:424)
        at java.lang.Thread.run(Thread.java:484)

This happens occasionally. At some point, both Apache and Tomcat become
sporadically unresponsive, and when you can get through, Apache gives an
Internal Server Error. The number of Tomcat-spawned java threads often seems to
spike around the same time.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>