[ https://jira.jboss.org/jira/browse/JBAS-5917?page=com.atlassian.jira.plug... ] Adrian Brock commented on JBAS-5917: ------------------------------------ You can reproduce this (at the moment) by running ./build.sh one-test -Dtest=org.jboss.test.jpa.test.WebLibsJPAUnitTestCase in the testsuite. However, once I've fixed JBAS-5912, you'll need to "break" the deployment by removing the persistence.xml or misname the peristence unit to reproduce the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5917?page=com.atlassian.jira.plug... ] Adrian Brock commented on JBAS-5917: ------------------------------------ The answer to your question depends upon what the "error" is. In general in JBoss5 we have "all or nothing" deployment. However there are cases where it allows the deployment to stay in the incomplete state, this is mainly for missing dependencies where deploying the missing dependency (a seperate deployment) will allow the deployment to complete without having to redeploy it. In that case, the incomplete state is not a problem because the application is not usable/accessible until the dependency exists. For an unrecoverable error like this example, the deployment should be removed, since it is unusable and unfixable without a redeployment. Here, you can see that the deployment has been removed, but there is still something lying around within Tomcat. It shows up as being able issue requests to the broken webapp which fails because the classloader no longer exists: 15:56:31,165 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing java.lang.IllegalStateException: BaseClassLoader@26154b{vfszip:/home/ejort/jboss-head/testsuite/output/lib/test-jpa-weblibs.war} classLoader is not connected to a domain (probably undeployed?) for class org.jboss.security.plugins.JBossSecurityContext at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:725) at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:374) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.security.SecurityContextFactory.getContextClass(SecurityContextFactory.java:142) at org.jboss.security.SecurityContextFactory.createSecurityContext(SecurityContextFactory.java:68) at org.jboss.web.tomcat.security.SecurityAssociationActions$4.run(SecurityAssociationActions.java:231) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.web.tomcat.security.SecurityAssociationActions.createSecurityContext(SecurityAssociationActions.java:227) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:81) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:325) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5917?page=com.atlassian.jira.plug... ] Remy Maucherat commented on JBAS-5917: -------------------------------------- Yes, it makes sense. Looking at the code, I can see a discrepancy when a problem occurs in one of the core components (like the loader; in standalone, this does not throw exceptions when starting it) compared with one of the application components (ex: a listener, etc). I'll try to address that in the next CR. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-5917?page=com.atlassian.jira.plug... ] Remy Maucherat resolved JBAS-5917. ---------------------------------- Resolution: Done The fix is now integrated in AS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira