Re: Scheduled WOApps not scheduled
Re: Scheduled WOApps not scheduled
- Subject: Re: Scheduled WOApps not scheduled
- From: Chuck Hill <email@hidden>
- Date: Thu, 27 Apr 2006 10:05:15 -0700
On Apr 27, 2006, at 12:37 AM, Wolfram Stebel wrote:
Hi List,
i have a WOApp running in 7 instances. Each night i scheduled one
of them to
restart at 3AM.
When i come to the server in the morning, one instance (the
scheduled one)
shows "refuse new session=ON" but there is no new log for the instance
showing up after restart.
So i suspect that the restart failes, only the refuse is set and
nothing
more.
I think you are probably mis-interpreting what is happening. The
application will not restart until all of the sessions have
terminated (unless you have configured it to restart when there are
some number of remaining sessions). What are you describing is what
happens when sessions get hung / deadlocked. Sessions in this state
are never checked back in and so never terminate. As the sessions
don't terminate, neither does the app. It just sits there in
shutdown mode waiting for the sessions to terminate and they never
will. So the problem is not that your app is not restarting, but
that it is not actually stopping!
I would suggest getting a thread dump from the application when it
is in this state, that should diagnose the problem. In your code,
the first thing to ensure is that the constructor, awake, sleep, and
terminate methods of session can't throw an exception ever.
Chuck
--
Coming in late 2006 - an introduction to web applications using
WebObjects and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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