Brian Stansberry wrote:
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.
Hmm, yeah maybe having a service as part of the deployment with some "artificial" dependencies preventing the connector to stop could do the trick. However this basically means that the connector cannot be stopped until the deployment is undeployed. Which might not even matter in case you use mod_cluster (at least for webapps).