[jboss-jira] [JBoss JIRA] (WFCORE-273) ServerInventory#reconnectServer should take auto-start into account

[Ken Wills (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182261#comment-13182261 ] 

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?



> ServerInventory#reconnectServer should take auto-start into account
> -------------------------------------------------------------------
>
>                 Key: WFCORE-273
>                 URL: https://issues.jboss.org/browse/WFCORE-273
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Emanuel Muckenhuber
>            Assignee: Ken Wills
>             Fix For: 3.0.0.Alpha1
>
>
> When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)