Re: GracefulApplication, gracefulTerminate() and JavaMonitor
Re: GracefulApplication, gracefulTerminate() and JavaMonitor
- Subject: Re: GracefulApplication, gracefulTerminate() and JavaMonitor
- From: Paul Hoadley <email@hidden>
- Date: Fri, 17 Jun 2016 15:49:15 +0930
On 15 Jun 2016, at 2:56 PM, Paul Hoadley <email@hidden> wrote:
> 1. I assume that setting "refuse new sessions” on an instance in JavaMonitor will eventually send a SIGTERM to the app which will be caught by the graceful shutdown mechanism. (Hitting the stop button in Eclipse, for example, doesn’t do that and so gracefulTerminate() isn’t called. You have to simulate it by sending SIGTERM to the Java process from a terminal.) That is, will this even work in production? (I can’t imagine the answer here is no, but would be good to know if anyone’s doing/done it.)
As far as I can tell, this assumption was wrong, so we’re not off to a good start. Hitting “refuse new sessions” for an instance (when it has no sessions—haven’t completed testing on an instance that’s also waiting for sessions to expire) eventually calls ERXApplication.refuseNewSessions(), which calls terminate(), regardless of whether er.extensions.ERXGracefulShutdown.Enabled is set true. The instance does do a graceful shutdown if I send it a TERM signal from the console, but that’s not really much help—I need this integrated with JavaMonitor.
Does anyone know what’s going on here? Was this feature just never hooked up with JavaMonitor properly, or am I doing something wrong? Anyone using GracefulApplication in any context?
--
Paul Hoadley
http://logicsquad.net/
_______________________________________________
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