I suggest this be controlled with a configuration flag rather than relying on the presence/absence of an mbean server. The behavior of moving an mbean through create/start/stop/destroy is not inherent in an mbean server; it's a special function of JBoss AS. So, you could have JBC running in the presence of an mbean server that would not call stop/destroy for you. Theoretically, you could also have JBC running in a pure microcontainer version of JBoss AS 5 where there is no mbean server. But that AS would still have its own ShutdownHook that takes care of create/start/stop/destroy and would not want JBC's own hook getting in the way. This is not an urgent thing; in the real world JBoss AS always has an mbean server, so the existing JBCACHE-1204 fix stops the problem of the JBC shutdown hook screwing up an AS shutdown. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106232#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...