Hi John, thanks for trying to fix my problem. Nevertheless, there are some points that need to be cleared here :
> 1. Figure out why there is "slow response time" and fix it. The slow response time has its origin in poorly designed SQL queries (that take up to 5 secs to execute...) but we are not responsible for this, nor are we in charge of the sql part in this project. So we need to cope with it. > 2. Train your users to only click once. It's impossible to train users to act according to your wishes. Maybe if the problem is simple and thus can understand why they must act differently, it's possible. In our case, we just can't tell them "please be patient, otherwise you'll throw Socket write errors exceptions" ;) > 3. Rotate your logs every 24 hours using logrotate. Logs rotate every 24 hours using the 'standard' logger included in Tomcat. > tell your developers to stop using System.out.println > for printing stack traces when they have an exception We don't. We use jsp error pages and manage exceptions gracefully. But in this case, we don't even get a chance to manage the exception by ourselves. Otherwise it would have been quite easy ^^ Here, Tomcat throws the exception and logs it WITHOUT asking anyone else. That's all it's about here. But thanks for trying to help ! -----Message d'origine----- De�: John Turner [mailto:[EMAIL PROTECTED] Envoy�: jeudi 24 juillet 2003 15:02 ��: Tomcat Users List Objet�: Re: Get rid of socket write error 1. Figure out why there is "slow response time" and fix it. 2. Train your users to only click once. 3. Rotate your logs every 24 hours using logrotate. 4. Use log4j and tell your developers to stop using System.out.println for printing stack traces when they have an exception. John Feltesse Julien wrote: > Hi, > > > We're using Tomcat 4.1.18. > Our problem is that when a client hits the "stop" button in his browser, > or double-click links, we can see in the logs : > > StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw > exception > org.apache.jasper.JasperException: Connection reset by peer: socket > write error > [...] > ----- Root Cause ----- > java.net.SocketException: Connection reset by peer: socket write error > > This is somehow logical, but may anyone know how to 'tell' Tomcat : > "When you trap such an error don't display it (or partially display it) > in the logs". > > In fact, in the company where the app runs the clients often hit twice > links because of slow response times. As a result, at the end of the day > the logs' size is HUGE compared to what it should be, because 2/3 of the > logs are filled with the long long long stack trace of the socket write > error... > > Thanks in advance. > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
