[jbossts-issues] [JBoss JIRA] (JBTM-2146) wsat-jta-multi_hop quickstart doesn't work

Paul Robinson (JIRA) issues at jboss.org
Mon Apr 7 08:08:13 EDT 2014


Paul Robinson created JBTM-2146:
-----------------------------------

             Summary: wsat-jta-multi_hop quickstart doesn't work
                 Key: JBTM-2146
                 URL: https://issues.jboss.org/browse/JBTM-2146
             Project: JBoss Transaction Manager
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Demonstrator, TxBridge, XTS
            Reporter: Paul Robinson
            Assignee: Gytis Trikleris
             Fix For: 4.17.19, 5.0.2


When running the wsat-jta-multi_hop quick start, the test fails:

(despite standalone-xts.xml is provided exactly how the instructions say + 127.0.0.1:9990 is accessible using the browser)

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.jboss.narayana.quickstarts.wsat.jtabridge.fromjta.BridgeFromJTATest
IV 06, 2014 2:10:16 DOP. org.jboss.arquillian.container.impl.MapObject populate
WARNING: Configuration contain properties not supported by the backing object org.jboss.as.arquillian
.container.remote.RemoteContainerConfiguration
Unused property entries: {serverConfig=standalone-xts.xml}
Supported property names: [managementPort, username, managementAddress, managementProtocol, password]

....

WARN: Cannot undeploy: test.war
org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: j
ava.lang.RuntimeException: java.net.ConnectException: JBAS012174: Could not connect to http-remoting:
//127.0.0.1:9990. The connection failed
        at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.undeploy(ServerDe
ploymentHelper.java:109)
        at org.jboss.as.arquillian.container.ArchiveDeployer.undeploy(ArchiveDeployer.java:55)
        at org.jboss.as.arquillian.container.CommonDeployableContainer.undeploy(CommonDeployableConta
iner.java:152)
        at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
ainerDeployController.java:205)
        at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(Cont
ainerDeployController.java:185)
        at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOper
ation(ContainerDeployController.java:271)
        at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(Co
ntainerDeployController.java:184)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
        at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
        at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
        at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploym
entContext(ContainerDeploymentContextHandler.java:78)


--
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 jbossts-issues mailing list