Hi Dave,

Well, I've seen this problem when I'm testing and I'm waiting patiently :) to 
get a response from an xml rpc service call.

Thanks

--- On Thu, 8/28/08, David Avendasora <[EMAIL PROTECTED]> wrote:
From: David Avendasora <[EMAIL PROTECTED]>
Subject: Re: broken pipe?
To: "Mersida Kurti" <[EMAIL PROTECTED]>, "WebObjects-Dev Mailing List List" 
<[email protected]>
Date: Thursday, August 28, 2008, 9:11 AM

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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com

This email sent to [EMAIL PROTECTED]



      
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to