[ https://issues.jboss.org/browse/JBTM-1957?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on JBTM-1957: ---------------------------------------- After changing the protocol to Servlet 3.0 I've started to struggle with JBTM-1128 and JBTM1217. It seems that all of this was a problem with Arquillian. I've changed the artifact arquilian container to 1.1.1.Final and it started to understand the jmx-as7 protocol (btw. the dependency to deployment.arquillian-service is not needed anymore). There was still a problem with IBM JDK and recovery tests. It seems that there could be some timing issue or the IBM JDK works differently in java.net.Socket class as controller.start receives exception from the ManagedDeployableContainer: http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.as/jboss-as-arq... In fact the server is not started and I did a (bit nasty) workaround which check reason of the exception and in case that the server seems to be started it does not re-throw the arquillian LifeCycleException up. https://github.com/ochaloup/narayana/commit/8026b5243e3cb207d48474998eb0d... -- 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