[jboss-dev-forums] [JBoss AS Development] - Re: Graceful Shutdown

bstansberry@jboss.com do-not-reply at jboss.com
Thu Dec 3 10:48:51 EST 2009


When I used "ad-hoc" about the connector start/stop, my meaning was the same as yours -- relying on the JMX notification is not good, as it's completely outside of how all other ordering is done, can break at any time etc.

The more I think about it, the more I like combining the per-webapp thingys into a single thingy that also handles the connector start/stop. It becomes:

GracefulStart:

Start the connector.

Graceful stop:

Coordinate with the deployed webapps and their session managers to go through all the details of draining sessions and ensuring in-flight requests have completed.
Stop the connector.

My experiment is going to follow this approach until it proves unworkable.

Re: install callbacks if the "central management bean" is deployed last; I have a vague recollection that I thought that wouldn't work for some other usage, but it did. But I could be misremembering, or maybe there was some weird fluke that made it work.

If that's a problem, we can just divide the "central management bean" into two parts:

Registry: deployed in bootstrap. Gets all the install callbacks
Invocation: deployed at the end. Has registry injected. Invokes on the registered items.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268814#4268814

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268814



More information about the jboss-dev-forums mailing list