Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 13069 invoked from network); 24 Sep 2003 14:23:50 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 24 Sep 2003 14:23:50 -0000 Received: (qmail 6776 invoked by uid 50); 24 Sep 2003 14:26:47 -0000 Date: 24 Sep 2003 14:26:47 -0000 Message-ID: <20030924142647.6775.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 22591] - Socket write error X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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.