[ https://issues.jboss.org/browse/WFCORE-1715?page=com.atlassian.jira.plugi... ] Yeray Santana Borges commented on WFCORE-1715: ---------------------------------------------- I have arrived to these conclusions after taking a look to the code around this issue: # It seems that the RestartMode has already a default value, created in the constructor of HostRunningModeControl. It's initialized to RestartMode.SERVERS in a single point: HostControllerEnvironment L298. Its setter is only invoked in HostProcessReloadHandler#reloadInitiated L145 so it seems that currently the default value used is RestartMode.SERVERS. # The possible "problem" could be if the user executes a reload(restartServers=false), this operation will let the HostRunningModeControl.RestartMode equals to RestartMode.HC_ONLY because it's never reverted to its default RestartMode.SERVERS after reloading the HC. The consequence I has been able to see is a minor different order when shutdown operation is executed after HC reload: Case 1: /host=master:reload(restart-servers=false) /host=master:shutdown(restart=true) Case 2: /host=master:reload(restart-servers=true) /host=master:shutdown(restart=true) Shutdown op on case 1, servers are unregistered from the HC, the HC is stopped and at the end the server are stopped. Shutdown op on case 2, servers are unregistered from HC, servers are stopped and at the end the HC is stopped. Whit the change in this issue, reverting RestartMode to its default after a HC reload, the sequence of actions of shutdown operation after a reload (with restart-servers true or false) will be the same and will be the sequences on case 2. [~brian.stansberry] About the default timeout, yes, I can confirm that it will be by default is 0 (code about timeout is in WFCORE-1427) -- This message was sent by Atlassian JIRA (v6.4.11#64026)