I've commented out the dependency of the WarDeployer on the TomcatClusteringCache as it was preventing the start of the 'all' config. This thread is to discuss how to restore the relevant dependencies. I expect this was failing because a bean loaded via the VFSDeployerScanner can't depend on a bean subsequently loaded via the VFSDeploymentScanner. The dependency arises from two causes: 1) If ClusteredSSO is used, the embedded Tomcat itself depends on the TomcatClusteringCache. The ClusteredSSO valve actually looks up the cache though based on an injected object name, and has some ill-considered code where it won't fail on start if the cache isn't there but rather waits to find it when it needs to service a request. So, expressing the dependency in the WarDeployer isn't strictly necessary, although removing it is hacky. 2) Distributable webapps need the cache for their sessions. This seems more straightforward -- it's the deployment that has the dependency, not the deployer. The WarDeployer should be able to add a dependency on the cache to any distributable webapp as part of the deployment process. It just needs to know the object name of the cache. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981961#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...