[ https://issues.jboss.org/browse/WFCORE-1427?page=com.atlassian.jira.plugi... ] Yeray Borges updated WFCORE-1427: --------------------------------- Description: In WildFly 10 we introduced the server suspend/resume and graceful shutdown feature. This feature allows the server to complete the active requests normally, without accepting any new requests. A timeout value specifies how long the suspend or shutdown operation waits for active request to complete. However, there are no specific operations to suspend/resume and shutdown gracefully all servers managed by a specific host controller. These operations can be applied only at server-group or whole domain level. The goal of this issue is to facilitate these tasks to the administrators. Additionally, the timeout attribute for all of those lifecycle operations will be renamed to suspend-timeout to avoid the confusion of this value with timeout applied to the entire operation. The suspend-timeout attribute has a meaning only for the timeout applied to suspend the servers. was: So instead of {code} :suspend(20) :reload {code} It's just {code} :reload(20) {code} The high level 'reload' command in the CLI should take a --timeout param as well. If doing the graceful suspend as part of server side ":reload" handling proves problematic (I haven't looked into it at all before filing this) then a simpler alternative is to only go with the --timeout param on the CLI reload command, and have the CLI implement the graceful behavior internally by first calling :suspend and then :reload. Web console could do the same thing. -- This message was sent by Atlassian Jira (v7.12.1#712002)