[jboss-jira] [JBoss JIRA] (AS7-2268) Domain member does startup instances

[ https://issues.jboss.org/browse/AS7-2268?page=com.atlassian.jira.plugin.s... ] Andreas Tauber commented on AS7-2268: ------------------------------------- Hi, I continued testing my configuration and like to provide some more information.I am seeing the following message in host-controller/boot.log 13:50:37,219 INFO [org.jboss.as.domain] (management-handler-threads - 1) JBAS010918: Registered remote slave host slave After the registration my slave is listed in the admin console and I am able to see my three instances server-four, -five, -six. The host-controller log on xp slave shows: 13:53:37,312 INFO [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-four 13:53:37,531 INFO [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-five 13:53:37,937 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS (Host Controller) 7.1.0.CR1b "Flux Capacitor" started in 18375ms - Started 9 of 9 services (0 services are passive or on-demand) The two servers with auto-start attribute are started, but the domain controller does not recognize it. They are not registered with domain-controller. I expected to see a message like the one I get for server-one, -two, -three on the domain controller: 13:49:03,580 INFO [org.jboss.as.host.controller] (proxy-threads - 2) JBAS010919: Registering server server-one So, the domain controller can "see" the four, five, six but does not register the correct status of the instances and is not able to start them remotely. Like mentioned the request for starting times out. Probably the communication from master domain controller to host controller does not work? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira