Major Description
Looking at the following log:
You will see that the server starts for the first test, but no scenario is ran:
16:37:24,606 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" started in 9755ms - Started 272 of 360 services (87 services are passive or on-demand) 16:37:24,783 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/hudson/workspace/narayana-xts-recovery-java6/jboss-as/build/target/jboss-as-7.1.2.Final-SNAPSHOT/standalone/data/content/9c/b09ed5c8a11739141e8a5b2e5eefb74c508183/content DEBUG [Remoting "endpoint" read-1] (WorkerThread.java:88) org.xnio.nio.WorkerThread.run(WorkerThread.java:88) - Started channel thread 'Remoting "endpoint" read-1', selector sun.nio.ch.EPollSelectorImpl@308bd98e DEBUG [Remoting "endpoint" write-1] (WorkerThread.java:88) org.xnio.nio.WorkerThread.run(WorkerThread.java:88) - Started channel thread 'Remoting "endpoint" write-1', selector sun.nio.ch.EPollSelectorImpl@384f33c1 DEBUG [Remoting "endpoint" task-4] (VersionedConectionFactory.java:129) org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:129) - Available version (Versions 0x01) DEBUG [Remoting "endpoint" task-4] (VersionedConectionFactory.java:135) org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:135) - Calling a stable server Apr 23, 2012 4:37:25 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill INFO: Hard killing of a server instance Apr 23, 2012 4:37:25 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: waiting for byteman to kill server Apr 23, 2012 4:37:36 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:37:47 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:37:58 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:09 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:20 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:42 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:53 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:39:04 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:39:16 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill
The trace output for this test is also empty:
