[ https://issues.jboss.org/browse/WFLY-1247?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-1247: -------------------------------------- So I have just been thinking a bit about how to implement this, and from a technical level I don't think it will be too hard. The important part is to control all the points at which a request can enter the server. I think the management API should look something like: Server Level: Add a timeout parameter to the :shutdown command. If this is larger than zero then a graceful shutdown will be performed, with a timeout as specified. Add :pause and :resume operations. These operations will allow you to halt all request processing without actually shutting it down. This could allow administrators to then make changes without requests in progress. Add some kind of server state attribute that allows you to read the server shutdown state (RUNNING, SHUTTING_DOWN, PAUSING, PAUSED). Deployment Level: Add a timeout parameter to the :undeploy command, that allows a deployment to be gracefully undeployed Add a :pause and :resume operations to a deployment to allow requests to a deployment to be halted. Add some kind of deployment state attribute that allows you to read the deployment shutdown state (RUNNING, UNDEPLOYING, PAUSING, PAUSED). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira