Re: App freeze problem

please please please do it one times:

kill -3 pidOfYourApp

after starting the app from the command line OR modifying 
SpawnOfWotaskd.sh as i explained it before. Then send the stacktraces 
to me or to the list.

thanks, david

Am 09.09.2004 um 06:58 schrieb Steven Pannell:

> Hi,
>
> This is will be no help at all I guess but I have the same problem 
> with WO
> 5.2.3.  Sometimes - not always - the application hangs with just 1 
> session.
> It has to be force quit.  I have 4 instances on different machines and 
> all 4
> hang the same way (never just one on it's own).  Which seems a bit of a
> strange coincidence if you ask me.
>
> In any case just to let you know, upgrading won't help.  I have no 
> idea what
> the problem is and I never get any kind of errors in logs.  This 
> problem has
> existed since WO 5.0
>
> Regards,
> Steve.
>
>
> -----
>
> Hi,
> I tried kill -3 <pid>, but the app would not quit. It
> would not quit through monitor and the monitor would
> not respond to requests for  WOSTATS for this
> instance. I have no option but to force quit(kill -9)
> this instance.
> EOAdaptor logging is on but nothing in the log. The
> strange thing is that there was only 1 active session
> for this instance, when it stopped responding. So
> doesn't seem to be a load problem. And all the other 9
> instances are running fine. All what the log says for
> this instance is:
> [2004-09-02 17:53:32 GMT] <WorkerThread8>
> <com.webobjects.appserver._private.WODefaultAdaptor>:
> Growing number of WOWorkerThreads to 32
> [2004-09-02 18:05:10 GMT] <WorkerThread23>
> <com.webobjects.appserver._private.WODefaultAdaptor>:
> Growing number of WOWorkerThreads to 64
> [2004-09-02 18:05:10 GMT] <WorkerThread23>
> <com.webobjects.appserver._private.WODefaultAdaptor>:
> Growing number of WOWorkerThreads to 128
>
> And max workerthread limit is 256. Thanks in advance
> for any clues.
>
> Davinder.
>
> --- David Teran <[email protected]> wrote:
>
>> Hi,
>>
>> did you try kill -3 yourAppPid ? This could give
>> hints about deadlocks.
>>
>> If you do this and see multiple threads sitting and
>> waiting
>> "object.wait()" then you probably have a deadlock. I
>> would be -very-
>> interested in the stacktrace.
>>
>> regards David
>>
>> Am 01.09.2004 um 01:26 schrieb davinder singh:
>>
>>> Hi,
>>> I'm facing problems similar to what were discussed
>> in
>>> the threads - Deadlock, I think and Growing Number
>> Of
>>> WOWorkerThreads. They were posted long back during
>>> WO5.1 days.
>>> I wonder, if anyone still faces these issues with
>>> WO5.2.3?
>>> To recall the problem the app just freezes, unable
>> to
>>> be controlled by monitor. I have to kill it and
>> the
>>> message in the log says:
>>> Growing Number Of WOWorkerThreads to 32
>>> Growing Number Of WOWorkerThreads to 64
>>> I'm using sharedEditingContext, properly unlocking
>>> them in finally{} and running 4 instances on a
>>> Mac10.3.5 server.
>>> Any suggestions???
>>> Thanks,
>>> Davinder.
>>>
>>>
>>> 		
>>> _______________________________
>>> Do you Yahoo!?
>>> Win 1 of 4,000 free domain names from Yahoo! Enter
>> now.
>>> http://promotions.yahoo.com/goldrush
>>> _______________________________________________
>>> WebObjects-admin mailing list
>>> [email protected]
>>>
>>
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>>>
>>
>>
>
>
> 		
> _______________________________
> Do you Yahoo!?
> Win 1 of 4,000 free domain names from Yahoo! Enter now.
> http://promotions.yahoo.com/goldrush
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>