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 4663] - Broken Pipe under some load
Date Thu, 08 Jan 2004 13:23:41 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=4663>.
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=4663

Broken Pipe under some load

glenn@apache.org changed:

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



------- Additional Comments From glenn@apache.org  2004-01-08 13:23 -------
As stated before this is not a bug.

This happens during normal operation of Tomcat when the web server side
tears down the tomcat connector socket due to the remote client terminating
its request prior to handling of the request by tomcat completing.

Here is what happens:

1.  Remote browser makes a request to web server.
2.  Web server sends request to tomcat via the JK connector.
3.  Tomcat starts processing request.
4.  Tomcat's output buffer fills so it sends it back to the
    web server via the connector socket.
5.  web server tries to write the buffer back to the remote
    client browser.
6.  The web server write to the remote client browser fails
    because the user hit STOP in their browser to abandon
    the request.
7.  web server process/thread detects this.  To free up resources
    since the request was abandoned the web server process/thread
    closes the connector socket to Tomcat.  Then it can recycle itself
    so it is available for another http request.
8.  On the Tomcat side it will fail when it tries to write additional
    output to the connector socket.  This triggers the exception you see.
9.  Now Tomcat can terminate processing the abandoned request if it
    hadn't been completed yet.

This is all perfectly normal.

Please do not reopen this.

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


Mime
View raw message