RE: many broken pipes, app stops responding

I was getting this problem with a project that I just recently
completed. I could figure it out for awhile but I speculated that it may
have to do with the fact that I had the development app running against
the beta app in production. When it was just the customer and I running
test the problem didn't show up much but as more test users were added
the issue showed up more so I made a copy of the database for
development and I didn't see the problem anymore. When I was researching
the issue I found a posting that talked about race conditions in the DB
cause this issue.

Hope this helps,
Ricardy

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Guido
Neitzer
Sent: Thursday, July 07, 2005 7:24 AM
To: [email protected]
Subject: Q: many broken pipes, app stops responding


Hi.

We have an application that sometimes stops responding after a while  
and I have a lot of similar entries in the log:

9807040 [WorkerThread7] WARN NSLog  - <WOWorkerThread id=7  
socket=Socket[addr=/6
2.153.135.49,port=59219,localport=2011]> Exception while sending  
response: java.
net.SocketException: Broken pipe

What happens here? What can I do to prevent, that the application  
stops responding? I deploy on Mac OS X with wotaskd and applications  
running as user root under Mac OS X 10.3.7, WO 5.2.3.

cug

_______________________________________________
WebObjects-admin mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-admin