[ https://issues.jboss.org/browse/ISPN-3531?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3531: -------------------------------- Summary: LifecycleManager of query module inadvertently unregisters MBeans belonging to other cache managers (was: LifecycleManager of query module keeps references to per cache manager resources (jmx related)) Description: The ObjectName used for query related MBeans does not contain the name of the cache manager as an attribute to ensure disambiguation. Thus, if two cache managers are configured to share the same JMX domain their query related MBean names would clash and shutting down one of the managers would also unregister the MBeans belonging to the other(s). (was: The resources in question are gathered when a cache manager is started and are used again when it is stopped. This does not work well if there are multiple cache managers that have different jmx domains. Cache stop event also does not seem to be processed correctly.) Edited title and description to match the new findings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira