Major Description
See: 172.17.131.2/job/btny-pulls-narayana/345/ where the job has hung for about 16hrs.
From looking at the stack trace in client.log (attached):
at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:107) at org.jboss.jbossts.txbridge.tests.inbound.junit.InboundBasicTests.setUp(InboundBasicTests.java:75)
The hang is happening on this line:
controller.start(CONTAINER);
Which is starting the container 'jboss', which is described in the arquillian.xml as:
<container qualifier="jboss" default="true" mode="manual"> <configuration> <property name="javaVmArguments">${server.jvm.args}</property> <property name="serverConfig">standalone-xts.xml</property> <property name="managementAddress">${node.address}</property> </configuration> </container>
From looking at server.log (attached) it looks like the server has started and deployed the deployments:
First of two deployments:
18:36:32,013 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "txbridge-inbound-tests-service.war" (runtime-name : "txbridge-inbound-tests-service.war")
Second of two deployments:
18:36:32,975 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "txbridge-inbound-tests-client.war" (runtime-name : "txbridge-inbound-tests-client.war")
Notice that the output above is that last line of output on the server.
