Re: JM does not see wotaskd-after some time
Re: JM does not see wotaskd-after some time
- Subject: Re: JM does not see wotaskd-after some time
- From: Paul Hoadley <email@hidden>
- Date: Sat, 6 Mar 2010 13:49:23 +1030
On 06/03/2010, at 4:52 AM, Chuck Hill wrote:
>> [2010-03-05 15:02:58 CET] <WorkerThread10> <WOWorkerThread id=10 socket=Socket[addr=/127.0.0.1,port=50809,localport=1085]> Exception while sending response: java.net.SocketException: Broken pipe
>>
>> Nevertheless, there's not many of them -- definitely such a report does NOT occur anytime JavaMonitor tries to connect to wotaskd and fails; the log occurs only occassionally.
>
> You can ignore that.
As an aside, what causes that broken pipe exception, and why is it safe to ignore, Chuck? I see it from time to time, though mostly in development.
--
Paul.
http://logicsquad.net/
_______________________________________________
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