Re: WO instance locks up and won't die.
Re: WO instance locks up and won't die.
- Subject: Re: WO instance locks up and won't die.
- From: Chuck Hill <email@hidden>
- Date: Tue, 18 Nov 2003 20:07:04 -0800
Hi Denis,
At 12:53 PM 19/11/2003 +1300, Denis Stanton wrote:
>About once a day I notice (in JavaMonitor) that the active session
>count is higher than it should be given that I only have a small number
>of users. Then my users will discover that they can't start a new
>session.
>
>They may actually find their sessions terminated, but they don't think
>in these terms so I'm not sure if that's what happens. They just say
>"The system is not letting me in"
>
It sounds as if your are deadlocking. Two common causes of this are
unbalanced locks to editing contexts (or other EO objects) and exceptions
in your code triggering bugs in WO that result in checked out sessions not
getting checked back in.
>I start a second instance and they're happy, but if I tell the first
>instance to refuse new sessions it never dies. In fact sometimes the
>session count increases despite the setting.
>
This can happen if there are direct action requests that specify the
instance number.
>You would expect that the
>session count would drop to zero as each times out.
Deadlock could explain this, as could sessions not getting checked back in.
>If the sessions
>are not working at all then users would have gone on to new sessions
>and the old ones would time out in an hour at most. If the sessions
>are still working for some users they should at least time out after
>the office is closed for an hour.
>
>Selecting stop does not close the instance. Restarting the computer
>does though.
>
Ya gotta worry when that doesn't work! ;-)
>I don't know what could be causing this or how to trace it.
>I'm using WebObject 5.2.1 on Mac OS X 10.2.8. 1 GB RAM. Total number
>of client computers that could be accessing my app = 6 (yes, six)
>
Are you locking your editing contexts? Do you see any exceptions or other
unusual messages in the app log? Search the archives here or at Omni for
'deadlock', lots of reading there. You should be able to quickly turn up
how to get a thread dump for your OS. That is the best way to diagnos what
is wrong.
HTH
Chuck
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.