[Solved by workaround]: wo adaptor produces "broken pipe"s

Thanks Chuck. We now were able solve the problem with a workaround.... 
for now.

Regards,
Will

On 07.12.2004, at 17:35, Will Scheidegger wrote:

> Thanks for the quick and helpful reply. We're bashing our heads 
> against the desk because we cannot seem to find the problem. We seem 
> to have db connection problems... but we have not yet figured out what 
> they are caused by.
>
> We'll keep trying... :-/
>
> Will
>
> On 07.12.2004, at 16:51, Chuck Hill wrote:
>
>> This message means, "the source of this request has closed the 
>> connection".  Often this means that the user has hit stop or 
>> navigated somewhere else.  In  your case it probably means that the 
>> app too so long to respond that the adaptor gave up and went to 
>> another instance.  Have the users been reporting "no instance 
>> available" or "your session has expired" errors?
>>
>> Unless you have changed the app, I would guess that you have some 
>> optimization work to do.  Likely you have exceeded some critical 
>> threshold in data size and processing is now taking longer than the 
>> woadaptor is prepared to wait.  Often this results from a slow fetch 
>> and simply adding a performance index will solve the problem.  
>> Otherwise, you will need to work on your code and / or start using 
>> the much dreaded WOLongResponsePage.  As an interim measure,  you can 
>> increase the Connect and Receive adaptor timeouts in JavaMonitor.
>>
>> I don't recall the CLOSE_WAIT problem being related to this.
>>
>>
>> Chuck
>>
>>
>> On Dec 7, 2004, at 7:00 AM, Will Scheidegger wrote:
>>
>>> We're facing a weird problem all of a sudden. This one app ran fine 
>>> for quite some time and now it chokes all the time and gives the 
>>> following feedback in the log file:
>>>
>>> [2004-12-07 15:52:53 CET] <WorkerThread14> <WOWorkerThread id=14 
>>> socket=Socket[addr=/192.168.1.40,port=
>>> 55917,localport=2007]> Exception while sending response: 
>>> java.net.SocketException: Broken pipe
>>>
>>> After a bunch of these entries, usually we have lots of CLOSE_WAITs 
>>> on the port of the application and the app becomes unavailable.
>>>
>>> Does anyone have a good idea on how to debug this? Thanks a bunch 
>>> for your help!
>>>
>>> Regards,
>>> Will
>>>
>>> _______________________________________________
>>> WebObjects-admin mailing list
>>> [email protected]
>>> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>>>
>> -- 
>> Practical WebObjects - a book for intermediate WebObjects developers 
>> who want to increase their overall knowledge of WebObjects, or those 
>> who are trying to solve specific application development problems.
>> http://www.global-village.net/products/practical_webobjects
>>
>>
>>
>
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin