org.jboss.as.test.integration.jca.deployment.WarServletDeploymentTestCase

org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase.enableLater: 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 web36

  • via GitHub by wildfly-ci
    , 11 months ago
    org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase.enableLater: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed
  • via GitHub by wildfly-ci
    , 11 months ago
    org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase.enableLater: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed
  • via GitHub by wildfly-ci
    , 11 months ago
    org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase.enableLater: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed
  • Stack trace

    • org.jboss.as.test.integration.jca.deployment.WarServletDeploymentTestCase: org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase.enableLater: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://[::1]:9990. The connection failed at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:319) at org.xnio.nio.WorkerThread.run(WorkerThread.java:559)

    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

    You’re the first here who have seen this exception.