[jboss-jira] [JBoss JIRA] (AS7-6230) Remoting "Read timed out" when starting multiple servers on a host
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Wed Jan 23 21:41:47 EST 2013
[ https://issues.jboss.org/browse/AS7-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750104#comment-12750104 ]
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]
Description of problem:
On single or a small number of CPU machine, launching number of (about 8 or above) servers at the same time like in the start-up results in 'org.xnio.channels.ReadTimeoutException: Read timed out'. In EAP 6.0.0, this can be avoided by longer time-out via 'jboss.host.server.connection.timeout' and 'jboss.host.domain.connection.timeout' system properties. But those time-out settings don't take effect in EAP 6.0.1 due to a mechanism change in DC<->HC communication.
How reproducible:
Always in the customer's environment.
Steps to Reproduce:
1. In a domain mode of EAP 6.0.1, set a number of servers (about 10) in host.xml.
2. Start the domain. All managed servers will start at the same time.
3. The following exception happens in the host controller.
Actual results:
[Host Controller] 16:15:58,036 ERROR [org.jboss.remoting.remote.connection] (Remoting "nceaptint03:MANAGEMENT" read-1) JBREM000200: Remote connection failed: org.xnio.channels.ReadTimeoutException: Read timed out
[Server:ib-demo-server1-group2] 16:16:00,236 ERROR [org.jboss.remoting.remote.connection] (Remoting "int03master:ib-demo-server1-group2:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 111bda67 to nceaptint03/172.16.139.60:9999
[Server:ib-demo-server1-group2] 16:16:00,704 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.client: org.jboss.msc.service.StartException in service jboss.host.controller.client: java.net.ConnectException: JBAS012174: Could not connect to remote://172.16.139.60:9999. The connection failed
[Server:ib-demo-server1-group2] at org.jboss.as.server.mgmt.domain.HostControllerServerClient.start(HostControllerServerClient.java:172) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
[Server:ib-demo-server1-group2] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
[Server:ib-demo-server1-group2] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
[Server:ib-demo-server1-group2] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
[Server:ib-demo-server1-group2] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
[Server:ib-demo-server1-group2] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
[Server:ib-demo-server1-group2] Caused by: java.net.ConnectException: JBAS012174: Could not connect to remote://172.16.139.60:9999. The connection failed
[Server:ib-demo-server1-group2] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118) [jboss-as-protocol-7.1.3.Final.jar:7.1.3.Final]
[Server:ib-demo-server1-group2] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:84) [jboss-as-protocol-7.1.3.Final.jar:7.1.3.Final]
[Server:ib-demo-server1-group2] at org.jboss.as.server.mgmt.domain.HostControllerServerConnection.openChannel(HostControllerServerConnection.java:158) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
[Server:ib-demo-server1-group2] at org.jboss.as.server.mgmt.domain.HostControllerServerConnection.connect(HostControllerServerConnection.java:86) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
[Server:ib-demo-server1-group2] at org.jboss.as.server.mgmt.domain.HostControllerServerClient.start(HostControllerServerClient.java:148) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
[Server:ib-demo-server1-group2] ... 5 more
[Server:ib-demo-server1-group2] Caused by: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 111bda67 to nceaptint03/172.16.139.60:9999
[Server:ib-demo-server1-group2] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:424) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:ib-demo-server1-group2] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:226) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:ib-demo-server1-group2] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:ib-demo-server1-group2] at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:ib-demo-server1-group2] at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:ib-demo-server1-group2] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:ib-demo-server1-group2] at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:ib-demo-server1-group2] at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:180) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:ib-demo-server1-group2] at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:ib-demo-server1-group2] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) [xnio-api-3.0.6.GA.jar:3.0.6.GA]
[Server:ib-demo-server1-group2] at org.xnio.nio.NioHandle.run(NioHandle.java:90)
[Server:ib-demo-server1-group2] at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
[Server:ib-demo-server1-group2] at ...asynchronous invocation...(Unknown Source)
[Server:ib-demo-server1-group2] at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:ib-demo-server1-group2] at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:ib-demo-server1-group2] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:ib-demo-server1-group2] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337) [jboss-remoting-3.2.8.SP1.jar:3.2.8.SP1]
[Server:ib-demo-server1-group2] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:74) [jboss-as-protocol-7.1.3.Final.jar:7.1.3.Final]
[Server:ib-demo-server1-group2] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:88) [jboss-as-protocol-7.1.3.Final.jar:7.1.3.Final]
[Server:ib-demo-server1-group2] ... 9 more
Expected results:
All managed servers should start normally regardless of the number of servers.
> 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
More information about the jboss-jira
mailing list