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: Chuck Hill <email@hidden>
- Date: Fri, 5 Mar 2010 22:07:51 -0800
On Mar 5, 2010, at 7:19 PM, Paul Hoadley wrote:
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.
It means the client (browser, wotaskd, etc.) closed its side of the
connection before the server side could send the response. This is
the result of a timeout or user action. The user hitting Stop in the
browser is a common cause, especially when the app is slow or an
action is taking a long time.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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