Ah... nothing else can be the cause of this? Asking because these aren't normal users for sure, must be something automated since I'm getting some 50 messages a minute :(
-----Original Message----- From: Peter Crowther [mailto:[EMAIL PROTECTED] Sent: terça-feira, 29 de Janeiro de 2008 16:31 To: 'Tomcat Users List' Subject: RE: Socket Exception > From: Nuno Manuel Martins [mailto:[EMAIL PROTECTED] > org.apache.tomcat.util.net.TcpWorkerThread runIt > SEVERE: Remote Host /xxx.xxx.xxx.xxx SocketException: Connection reset [...] > Anyone on the list knows what this is, what might be causing > it and how do I fix it? The usual cause is that the browser's stopped a HTTP request part-way through, generally because the user's navigated to another page before the first page has completely downloaded. The browser closes the connection, with the result that Tomcat gets an exception when it next tries to write data to the socket. Arguably it shouldn't be logged as a SEVERE error on production systems, but getting that log message during development and stress testing can be very handy! Fix it by any of the following (in increasing order of difficulty): 1) Ignore it (and change any log-reading scripts that look for SEVERE errors to ignore this one); 2) Grab the source for 5.0.28, find the line where this is logged and change the logging level in the case of a connection reset error, then recompile Tomcat; 3) Educate your users that they are supposed to sit on their hands until the page has completely loaded (by far the hardest ;-) ). - Peter --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
