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

[ALRubinger]

"ALRubinger" wrote : The key concept is to separate internal requests from external requests, with the acceptor acting as a gate on the external requests. So graceful shutdown ends external requests, while still leaving the possibility of internal requests, e.g. web tier calling into an EJB. For the internal requests, the normal dependency mechanism (web app depends on ejb) ensures the EJB doesn't undeploy before the webapp is undeployed.

To copy myself a bit from a #jboss-dev IRC talk:

What's an invocation which was triggered by an EJB Timer; internal or external?  While I like the notion of separating out acceptors/processors, I think the context of the request/session in progress is not always so clear.  

Also we've talked about a separation between services and deployments.; but services are deployments themselves.  Deployments may depend both upon each other and upon services.  Services may depend upon each other.  In this light I think the standard MC dependency mechanism will suffice. 

To me the tricky part is extracting out all the endpoints (acceptors) and ensuring all moving parts are explicitly wired together.

S,
ALR

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

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