This behavior results from HTTP protocol. Each new page request results in a new TCP connection. When a user press STOP or RELOAD button or goes to another page the browser resets the old connection resulting this exception on server side. Do not worry about, just properly handle it or you can ignore it also. Or another option use TC4.x
-----Original Message----- From: A mailing list about Java Server Pages specification and reference [mailto:[EMAIL PROTECTED]]On Behalf Of [NGUYEN Duc Hai] Sent: Wednesday, February 05, 2003 4:28 PM To: [EMAIL PROTECTED] Subject: my error... Hi all, Sorry for my following question because it seems stupid :( I don't know why I touch always the following error : 2003-02-05 11:43:52 - Ctx( /pondi ): IOException in: R( /pondi + /images/Fichier-BatTypePro.jpg + null) Connection abort ed by peer: socket write error I use Tomcat Server 3.2.3 and JDK 1.3 Thanks a lot NGUYEN =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant archives, FAQs and Forums on JSPs can be found at: http://java.sun.com/products/jsp http://archives.java.sun.com/jsp-interest.html http://forums.java.sun.com http://www.jspinsider.com
