[
https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5887:
---------------------------------------
The critical problem here is that there is no automatic reconnection if via the process
controller the HC can see the server is still alive. The timeout might need tweaking, but
the key thing is getting the server reconnected.
If the server reconnects, there won't be an issue as long as there were no commands
attempting to modify that server in the interim -- with such a poorly timed modification
being unlikely. If there were a mod, the HC knows the reconnecting server is out of sync
and marks it as requiring restart.
CLONE - Host controller unregisters server after it doesn't
respond for 30 seconds; doesn't reconnect
-----------------------------------------------------------------------------------------------------
Key: AS7-5887
URL:
https://issues.jboss.org/browse/AS7-5887
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP)
Reporter: Travis Rogers
Assignee: Emanuel Muckenhuber
Fix For: 7.2.0.CR1, 7.1.4.Final (EAP)
Simple test to reproduce:
(kill -STOP <pid>, 30 seconds later, receive "unregistered" message in
the host controller. After restarting (kill -CONT <pid>), no longer able to control
instance via the host controller.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira