java.io.IOException

java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web31868

  • via GitHub by wildfly-ci
    , 10 months ago
    java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed
  • via GitHub by wildfly-ci
    , 10 months ago
    java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed
  • via GitHub by wildfly-ci
    , 7 months ago
    java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed
  • Stack trace

    • java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75) at org.jboss.as.test.shared.ServerReload.getContainerRunningState(ServerReload.java:136) at org.jboss.as.test.shared.ServerReload$SetupTask.reloadIfRequired(ServerReload.java:201) at org.jboss.as.test.shared.ServerReload$SetupTask.setup(ServerReload.java:184) at org.jboss.as.test.shared.ServerReload$BeforeSetupTask.setup(ServerReload.java:144) at org.jboss.as.test.integration.security.common.AbstractSecurityDomainsServerSetupTask.setup(AbstractSecurityDomainsServerSetupTask.java:118) at org.jboss.as.arquillian.container.ServerSetupObserver.handleBeforeDeployment(ServerSetupObserver.java:116) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:122) at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:258) at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71) at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:162) at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:143) at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:64) at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:139)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Once, 1 year ago
    6 times, 7 months ago
    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    2 more bugmates