Re: Broken Pipe
Re: Broken Pipe
- Subject: Re: Broken Pipe
- From: Denis Stanton <email@hidden>
- Date: Tue, 9 Dec 2003 19:38:30 +1300
George
I'm sure others will correct me if I am wrong, but I believe the
message "Broken pipe" is WebObject's way of telling you that by the
time it had an answer ready to send the browser was no longer listening.
If you get tired of waiting for a response and you click again, then WO
registers the latest request from your browser. Then when the earlier
request is ready to send back it finds the connection has been taken
over by the new request. It's pipe back to the browser is broken.
Maybe there are other reasons for the message. Maybe your request is
really taking too long, but one easy way to get a broken pipe is just
to click two on the web page before the last click was answered.
Denis
On Tuesday, December 9, 2003, at 11:59 AM, George Domurot wrote:
this error is in the development environment
On Dec 8, 2003, at 3:11 AM, Pierre Bernard wrote:
This most likely means that either the adaptor or your web browser
timed out waiting for a response.
Try setting the adaptor timeouts from within JavaMonitor.
A current app I'm working freezes up for about a minute when calling
editingContext.saveChanges. The following message is added to the
system output:
<WorkerThread3> <WOWorkerThread id=3
socket=Socket[addr=/xxx.xxx.xxx.xxx,port=51634,localport=51563]>
Exception while sending response: java.net.SocketException: Broken
pipe
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.