Re: broken pipe?
Re: broken pipe?
- Subject: Re: broken pipe?
- From: Pascal Robert <email@hidden>
- Date: Thu, 28 Aug 2008 09:37:12 -0400
It can also be that a request is taking long, and the browser will
drop the TCP connection. You either have to speed up the thing or use
WOLongResponsePage if it's « normal » that the request takes a long
time.
I see this Warning when a user gets impatient and instead of waiting
for a long-running process to finish, they navigate to another page.
It's basically the app saying "I tried to return the requested page
to the user, but the connection (pipe) back to the browser was broken"
In other words, it is another symptom of the problem causing things
to run slow, not the cause.
Dave
On Aug 28, 2008, at 8:59 AM, Mersida Kurti wrote:
Hi everyone,
Wondering if anyone has seen this error before. We're seeing it
when our database becomes hung up (not sure why), and the user is
getting a timeout error. Anyone has a clue as to why this is
happening...you seen this before? We've noticed that when we
restart the database everything goes ok for a few days then it
starts happening again.
<WOWorkerThread id=0 socket=Socket[addr=/
xxxxxxxxxx,port=56xxx,localport=2002]> Exception while sending
response: java.net.SocketException: Broken pipe
Thanks in advance.
Mersida
_______________________________________________
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