Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] created the discussion "Re: Overall control of graceful shutdown" To view the discussion, visit: http://community.jboss.org/message/563085#563085 -------------------------------------------------------------- The GracefulShutdownTerminator would be registered in start(StartContext). If the shutdown isn't meant to be graceful, the MSC would trigger an overall stop (probably by stopping a root service all the others depend on) and then would immediately invoke all the GracefulShutdownTerminators. So waiting until stop() to register the terminator would not work. I smell a possible race there though even with registering in start(). Your question about the deployments/connector gets into the real heart of the issue, how subsystems and services that are part of a deployment can be composed such that the dependencies work out. I think it's worthwhile to think through how to do that, since whether or not the GracefulShutdownTerminator idea makes sense, using the MSC dependency mechanism is very likely going to be needed to get graceful shutdown to work. For example, as *part* of a war deployment there could be a service that monitors the existence of active sessions during shutdown. It depends on some other service in the deployment (e.g. the session manager) and on the connector. The connector will not stop until that service stops. That service registers the GracefulShutdownTerminator. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563085#563085] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] created the discussion "Re: Overall control of graceful shutdown" To view the discussion, visit: http://community.jboss.org/message/563147#563147 -------------------------------------------------------------- The dependencies aren't really artificial. The service that depends on the connector has a real job to do -- figuring out when long running work the needs an open connector is completed. It will of course delegate to other services for a lot of things, but I bet it will end up having some significant logic. If mod_cluster is integrated then part of what it does could be to interact with mod_cluster to trigger sending a global DISABLE_APP to httpd. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563147#563147] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Emanuel Muckenhuber [http://community.jboss.org/people/emuckenhuber] created the discussion "Re: Overall control of graceful shutdown" To view the discussion, visit: http://community.jboss.org/message/563312#563312 -------------------------------------------------------------- I guess the startup could be different from case to case, but we could provide a way to register a runnable we run after deployment completed. More precisely a service using the asynchronous() feature of msc and registering a runnable which does something like:     public void run() {         try {             connector.start();             startContext.complete();         } catch (Throwable t) {             startContext.failed(new StartException(t));         }     }     public void run() {         try {             connector.start();             startContext.complete();         } catch (Exception e) {             startContext.failed(new StartException(e));         }     } -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563312#563312] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Brian Stansberry [http://community.jboss.org/people/bstansberry%40jboss.com] created the discussion "Re: Overall control of graceful shutdown" To view the discussion, visit: http://community.jboss.org/message/563583#563583 -------------------------------------------------------------- A problem we've had in the past with not stopping endpoints early as  part of graceful shutdown is the invocation has returned from the  deployment code, so the deployment and its CL are unloaded. But the  invocation is still alive on it's return path, it hasn't passed yet  through the response marshalling logic in the endpoint. As a result,  when it hits the response marshalling logic, calls are made to the  unloaded CL, and they fail. This is more of an issue with EJBs. Web requests happily don't do any marshalling in the connectors. :) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563583#563583] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Emanuel Muckenhuber [http://community.jboss.org/people/emuckenhuber] created the discussion "Re: Overall control of graceful shutdown" To view the discussion, visit: http://community.jboss.org/message/563597#563597 -------------------------------------------------------------- I see. Hmm, doesn't this problem exist in general when you have multiple EJB deployments using the same endpoint (not sure how this works exactly) - but in the end it might happen that one deployment can be shut down gracefully faster than another, where the endpoint can't be closed? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563597#563597] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]