Re: Quite a few broken pipes - is this a problem ?

hi jonathon -

thanks for your mail - interesting last point, which raises another 
question! is the "Average Transaction Time" on the WOStats page a good 
indication of the average length of time a user has to wait for the 
application to respond ?

thanks, simon

On 27 Jan 2004, at 17:26, Jonathan Rochkind wrote:

> That probably does not indicate a problem.
>
> I believe that if the browser drops the connection before the WO app 
> has returned the complete response, you get this line in the log. The 
> browser dropping the connection can happen for several reasons, some 
> of which aren't a problem at all (the user pressed the stop button, or 
> quit their browser, or whatever), some of which might indicate a 
> problem (the request was taking so long, the browser gave up on 
> it---why was it taking so long, that might be a problem).
>
> Hope this helps,
> --Jonathan
>
> At 5:14 PM +0000 1/27/04, Simon wrote:
>> hi all,
>>
>> i have been trawling through the logs of one of out deployed apps 
>> (note: i fixed the missing-logs issue i wrote to the list about a 
>> week or so ago - the problem was a permissions issue with the folder 
>> i was dumping the logs to) and there seems to be quite a few 
>> "java.net.SocketException: Broken pipe" exceptions dotted about.
>>
>> i'm trying to figure out if i should be worrying about them, or 
>> whether they are just normal deployment output ? and what kind of 
>> thing causes these exceptions ? the app seems to be otherwise happily 
>> running.
>>
>> thanks for any advice or pointers,
>> simon
>>
>> _______________________________________________
>> WebObjects-admin mailing list
>> [email protected]
>> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin