[jboss-jira] [JBoss JIRA] (AS7-6444) Physical Server Shutdown (SLAVE Host Controller) doesn't unregister JBOSS server from Domain Controller (MASTER)

[Tomaz Cerar (JIRA)]

     [ https://issues.jboss.org/browse/AS7-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar updated AS7-6444:
-----------------------------

    Component/s: Domain Management

    
> Physical Server Shutdown (SLAVE Host Controller) doesn't unregister JBOSS server from Domain Controller (MASTER)
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-6444
>                 URL: https://issues.jboss.org/browse/AS7-6444
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.1.Final
>         Environment: JBOSS AS 7.1.1.Final
>            Reporter: Murtaza Ghodawala
>
> Hello Sir/Madam,
> We have one master (domain controller) and one slave (host controller) jboss AS 7.1.1.Final setup. Whenever the physical server starts up, JBOSS service starts up automatically and same way on physical server reboot JBOSS gets shutdown and started along with the physical server startup.
> Our problem is when we try to reboot slave machine and after reboot if we check the logs, it states ERROR message and because of which slave JBOSS server (host controller) doesn't get started up.
> [Host Controller] 15:35:26,241 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: org.jboss.as.host.controller.RemoteDomainConnectionService$HostAlreadyExistsException: JBAS010832: There is already a registered host named 'slave'
> The above problem is similar to the one raised in this JIRA BUG and hoping for a quick reply.
> Thanks and Regards,
> Murtaza Ghodawala
> Email: murtaza_ghoda82 at hotmail.com
> Mobile: +965 97180549

--
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