The test module uses cargo to deploy applications to a server, but it doesn't actually check if the web application has been deployed or not before continuing. This hasn't cause too many problems so far as Tomcat and JBoss seem to deploy things quickly enough. When moving to do tests on other containers, this is not always the case and this can cause tests to fail. One solution for this would be to use cargo URLDeploymentMonitors to make sure that the web application is pingable before continuing (cargo uses this method to check when a server is started using the cargocpc.war). This would require that all test web applications to not display a 404 page when its context is access. Would this be an acceptable change to require all web applications to have a pingable context? Note: ideally cargo would have some sort of other deployment monitor that could be used more transparently using the server logs, jmx, etc. But this is currently not the case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153447#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...