[jboss-jira] [JBoss JIRA] (AS7-6230) Remoting "Read timed out" when starting multiple servers on a host

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on AS7-6230:
----------------------------------------------

Osamu Nagano <onagano at redhat.com> made a comment on [bug 903453|https://bugzilla.redhat.com/show_bug.cgi?id=903453]

Besides the case 00756264, there was a communication between the customer and a RH developer on the community thread [1].  And the developer introduced a new system property 'org.jboss.as.host.start.servers.sequential' in the code [2], to start the servers sequentially to avoid the exception.  This feature works well for the customer and I figured out the necessary 6 commits from his branch to apply on EAP_6.0.1.GA.

pick 793ba23 [AS7-5556] Where we convert to a String ensure we set the charset to UTF-8 for both processes.
pick 25bfd87 Fix wrong unmarshalling order of process inventory data.
pick d3cdd74 [AS7-5887] reconnect servers automatically
pick f3e0b72 add managed server std.in state
pick 1ed0175 [AS7-6230] wait until the managed server opens it's mgmt channel by default
pick 2d956ec [AS7-6230] add a blocking start property for the host-controller

[1] https://community.jboss.org/thread/215769
[2] https://github.com/jbossas/jboss-as/pull/3794
                
> Remoting "Read timed out" when starting multiple servers on a host
> ------------------------------------------------------------------
>
>                 Key: AS7-6230
>                 URL: https://issues.jboss.org/browse/AS7-6230
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: Emanuel Muckenhuber
>            Assignee: Emanuel Muckenhuber
>             Fix For: 7.2.0.CR1
>
>
> Apparently when starting multiple servers on a host some of them fail to connect to the HC and the remote connection times out. 

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