Re: Broken Pipe
Re: Broken Pipe
- Subject: Re: Broken Pipe
- From: Alexander Spohr <email@hidden>
- Date: Sat, 6 Dec 2003 12:43:12 +0100
clue:
your webserver (or browser if using direct connect) gave up to wait for
response of your app. so it closed the pipe on which it was listening.
your apps worker thread just tells you that.
has nothing to do with eof.
atze
Am 06.12.2003 um 00:14 schrieb George Domurot:
WO List:
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
The odd thing is that no exception is actually being thrown and the
changes are saved to the database.
Any clues out there about what this message means?
Thanks for any input,
George
_______________________________________________
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.
_______________________________________________
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.
| References: | |
| | >Broken Pipe (From: George Domurot <email@hidden>) |