Re: java.net.SocketException: broken pipe
Re: java.net.SocketException: broken pipe
- Subject: Re: java.net.SocketException: broken pipe
- From: Art Isbell <email@hidden>
- Date: Sun, 9 Jul 2006 09:25:58 -1000
On Jul 9, 2006, at 4:49 AM, Frank Gibau wrote:
Could there by another reason for: java.net.SocketException: broken
pipe
This can occur when the WO app doesn't respond within the WO HTTP
adaptor's receive timeout; e.g., when database access during the
response is slow. If this happens, the user would see a "No instance
available" message even though the instance is actually available but
just too slow. A browser refresh can produce the expected response
in some situations.
This can also occur if the user cancels her request prior to the
response being received.
Neither of these situations should disable the instance. However,
if you see this message, the instance has become unresponsive, and
JavaMonitor is unable to stop it without force quitting it, the
instance could be deadlocked. A common cause of WO instance deadlock
is improper locking/unlocking of editing contexts that aren't
Session's default editing context.
Aloha,
Art
_______________________________________________
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