[jboss-jira] [JBoss JIRA] (AS7-3819) AS testsuite hangs when set to IPv6

[ https://issues.jboss.org/browse/AS7-3819?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-3819: ------------------------------------------ This last probl;em may be a bug or it may be a configuration building issue: {noformat} 19:04:25,464 INFO [org.jboss.as.ee.deployment.spi] (Thread-37) JBAS016100: Begin deploy: [target=http://org.jboss.as.ee.deployment/jsr88?targetType=as7,parent=null,type=ejb,id=file:/tmp/deployment-ejb.jar] 19:04:25,469 INFO [org.jboss.remoting.endpoint] (Thread-37) Connecting to destination address /127.0.0.1:9999 19:04:25,475 INFO [org.jboss.remoting.endpoint] (Thread-37) Connecting to destination address /127.0.0.1:9999 19:04:30,480 ERROR [org.jboss.as.ee.deployment.spi] (Thread-37) JBAS016153: Operation Distribute failed on target: org.jboss.as.ee.deployment.spi.DeploymentManagerTarget@b0014f0: java.lang.RuntimeException: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:113) at org.jboss.as.controller.client.helpers.standalone.impl.ModelControllerClientServerDeploymentManager.executeOperation(ModelControllerClientServerDeploymentManager.java:47) at org.jboss.as.controller.client.helpers.standalone.impl.AbstractServerDeploymentManager.execute(AbstractServerDeploymentManager.java:79) at org.jboss.as.ee.deployment.spi.DeploymentManagerTarget.executeDeploymentPlan(DeploymentManagerTarget.java:195) at org.jboss.as.ee.deployment.spi.DeploymentManagerTarget.deploy(DeploymentManagerTarget.java:118) at org.jboss.as.ee.deployment.spi.DeploymentWorker.run(DeploymentWorker.java:64) Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://127.0.0.1:9999. The connection timed out at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166) at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:166) at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:138) at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:62) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:106) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:89) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:252) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:151) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeAsync(AbstractModelControllerClient.java:111) ... 5 more {noformat} ProtocolChannelClient is definitely being passed the wrong URI of remote://127.0.0.1:9999. -- 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