Antw: Re: Prevent "Connection reset by peer" message to be shown in log file
Antw: Re: Prevent "Connection reset by peer" message to be shown in log file
- Subject: Antw: Re: Prevent "Connection reset by peer" message to be shown in log file
- From: "Andri vonAllmen" <email@hidden>
- Date: Wed, 14 Jul 2010 11:04:48 +0200
>>> Chuck Hill <email@hidden> schrieb am Dienstag, 13. Juli 2010 um
16:17 in Nachricht <email@hidden>:
> On Jul 13, 2010, at 1:59 AM, Andri vonAllmen wrote:
>
>> Hi List,
>>
>> some users like to double-click everything (or they have some kinetic tremor
> or whatever). This produces a lot of messages like the one shown below:
>>
>> [2010-07-13 10:44:19 CEST] <WorkerThread6> <WOWorkerThread id=6
> socket=Socket[addr=/10.0.10.82,port=3014,localport=2001]> Exception while
> sending response: java.net.SocketException: Connection reset by peer: socket
> write error
>>
>> Is it possible to filter out these messages before they are written into the
> respective applications log file?
>
> Not that I know of.
>
>
>> How is it done? In my case, about 99% of all messages in the different log
> files are such messages.
>
>
> If it is that frequent, I would look for other sources of the error (unless
> you are not writing much to the log). Are you using Ajax wrong? Is there
> something on your network causing this?
>
I'm not using Ajax. The error also occurs if running the application locally and without a webserver in between. Besides the error message in the log files (or console), no unwanted or weird behaviour is noticeable.
In the meantime I found out, that this error occurs if using Microsofts Internet Explorer only (no matter which version). If using other browsers, an error occurs as well (also a SocketException, but not the same message), but less frequently (hardly ever reproducable).
Somehow I think, it makes sense, that a response can't be send if performing a double-click on a hyperlink (which is stupid anyway), since this causes two responses to be sent, but just one is acceptet by the browser. But the error doesn't occur in a new, clean project (just tried that out). So it will most likely be some misadjustment or false programming. But since the project is huge and it is too hot here in Switzerland, my brain denies mental work. Maybe I'll take a look at it again in winter (the error occured for the last 10 years anyway).
>
> Chuck
--- Disclaimer: --------------------------------------------------------- This email and contents is for use only by the intended recipient. If you are not the individual or entity to whom it is addressed, you are hereby formally notified that any use, copying or distribution of this email and attachments, in whole or in part, is strictly prohibited. If you have received this email in error, please notify the sender and delete the message and attachment(s) from your system. Any views, opinions or information, expressed or contained in this email, are those of the sender and not necessarily reflect those of CEDES. To help protect our environment, please avoid printing out this information unnecessarily.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden