[ https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin... ] Ken Wills commented on WFCORE-273: ---------------------------------- After doing quite a bit of testing on this, the bug has either been fixed by one of the other changes in this area, or I'm just not seeing it. A server marked with auto-start="false" that is started, is shown stopped and shown as disabled after HC reload and disconnect / reconnect of the HC and various other combinations, both on the master HC and slaves. It appears the attribute update-auto-start-with-server-status was added to track the running states across reloads, and with this enabled the last running state is reflected correctly (auto-start=false / update-auto-start-with-server-status = true and server = RUNNING, after a HC reload the server is correctly restarted). [~bstansberry] Do you happen to remember anything else about this bug? -- This message was sent by Atlassian JIRA (v6.4.11#64026)