I think Chuck is right. One thing that most J2EE / web applications do not do is to catch the IOError the container is supposed to throw when the browser / client disconnects and closes the socket. That way the answering thread can immediately stop its work, clean up, and go home.
Tim -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Sunday, February 05, 2006 1:21 AM To: Tomcat Users List Subject: RE: Would like to know what might be causing this exception in servlet > From: Richard S. Huntrods [mailto:[EMAIL PROTECTED] > Subject: Would like to know what might be causing this > exception in servlet > > Feb 1, 2006 9:09:33 PM org.apache.tomcat.util.net.PoolTcpEndpoint > processSocket > SEVERE: Socket error caused by remote host /204.244.137.23 > java.net.SocketException: Connection reset I believe this is just expected behavior when the peer closes its end of the TCP session (e.g., user closes the browser before a response is delivered), before the SSL negotiation is completed. No workaround or fix needed. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
