JBossCacheManager prevents stopping and restarting webapp via JMX

The JBossCacheManager's start() method tries to install two valves using JMX calls. This works fine during a normal deployment, but fails if the webapp Context is stopped and then started via JMX operations (JMX console or twiddle).

The issue is the Tomcat StandardContext's start() method unregisters itself from the JMX server before calling the JBossCacheManager's start() method. It then re-registers itself later on. The JBossCacheManager tries to install 2 valves using JMX, which fail with a InstanceNotFoundException.

This doesn't show up during normal app deployment because there the deployer starts the context and then adds the manager to the context. By the time the manager is added, the context is registered.