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/09/24 16:26:47 UTC

DO NOT REPLY [Bug 22591] - Socket write error

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

Socket write error





------- Additional Comments From jms@mail.de  2003-09-24 14:26 -------
I think this happens if the client browser sends a request (GET), but then
cancels the request by pressing STOP or hitting escape. Tomcat then tries to
send the result, but the receiver has already gone. This is just normal, but you
are right:
tomcat should catch this exception because it is quite normal and happens very
often.