&quot;adrian(a)jboss.org&quot; wrote : | This can obviously be fixed, but I guess what should really be happening | is the ProfileService undeploys in reverse order of stages, | i.e. APPLICATION then DEPLOYER then BOOTSTRAP. | | The MainDeployer.shutdown() should just be there to catch things | that don't undeploy themselves properly. | | The problem is that the Profile api doesn't guarantee any ordering | | | Collection<VFSDeployment> getDeployments(DeploymentPhase phase) throws Exception; | | | Certainly the phases should be undeployed in reverse order. If needed the deployments api could express ordering using a List, but should that be necessary? If it started correctly it should stop correctly unless new dependencies are being accessed during shutdown. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123624#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...