[
https://issues.jboss.org/browse/WFCORE-273?page=com.atlassian.jira.plugin...
]
Ken Wills commented on WFCORE-273:
----------------------------------
Actually, I think I may have been able to figure out how to cause this:
(1) Start master & slave HCs
(2) kill master HC
(3) connect to slave HC and start a non-auto-start server
(4) restart master HC
(5) server shows up in master as disabled, but is running.
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)