Ok, so the dependencies just seem broken/unresolvable and I'm not sure why this would work in general. The problem I see is that: HAJNDI injects JBossCacheDistributedTreeManager.cache which is injected from HAPartitionCacheHandler.cache HAPartitionCacheHandler another bean, either DistributedState or HAPartition to initialize its cache by calling acquireCache(), but HAPartitionCacheHandler cannot depend on these because they depend on HAPartitionCacheHandler in order to call methods on it! What is happening right now is that the JBossCacheDistributedTreeManager.clusteredCache property is being injected from the HAPartitionCacheHandler bean cache property, but the cache property has not been set. The mc is assuming that since the HAPartitionCacheHandler is started, its properties are valid. This is not the case. Adding a dependency to the JBossCacheDistributedTreeManager on HAPartition is not changing when the clusteredCache property is set. The HAPartitionCacheHandler does not appear to be a valid bean in terms of dependency injection. I'm curious how this works before my reorg of deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181999#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...