[ https://issues.jboss.org/browse/ARQ-1455?page=com.atlassian.jira.plugin.s... ] David Mann updated ARQ-1455: ---------------------------- Description: When using the BOMs as suggested in http://www.jboss.org/jdf/stack/stacks/, the dependencies given for ARQ Core and JBossAS managed runtime seem to be wrong, as can be seen in the effective POM. I'm not quite sure if you guys are the ones to address this to, but it led to some very strange bugs while trying to establish ARQ support in an existing project. For instance, ARQ starts the container just fine, then times out with - org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start container - Managed server was not started within [60] s Maybe someone should look at the JDF stacks pages as well. Perhaps you know who to talk to? The versions there just don't seem right, there is no entry for the 7.1.3.Final runtime, the forge plugin for the stacks doesn't seem to work, and if it did, it wouldn't generate the correct dependeny to ARQ anyway, and so on. After having sunk 1 night into figuring all this out, I have learned a lot and everyting is working now. :-) This bug report is mainly to help people that run into the same problem. Kind regards, and cheers for an awesome product :-) David was: Someone should add the following to the arquillian getting started tutorial (http://arquillian.org/guides/getting_started/) <!-- Force the use of the Servlet 3.0 protocol with all containers, as it is the most mature --> <defaultProtocol type="Servlet 3.0" /> See attached test case, which can be resolved using the snippet above. -- 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