[infinispan-issues] [JBoss JIRA] (ISPN-3531) LifecycleManager of query module keeps references to per cache manager resources (jmx related)

[Adrian Nistor (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922256#comment-12922256 ] 

Adrian Nistor edited comment on ISPN-3531 at 11/11/13 5:53 AM:
---------------------------------------------------------------

I've revisited this issue and found that my initial analysis was completely wrong, the title and description are completely inaccurate, but there still is an issue here with the unregistering of MBeans during cache stop; a bit different one though.

First of all, the problem I noticed initially was the MassIndexer MBean disappearing from the MBean server if there were two cache managers and one of them was shut down at some point. My problem was that the MassIndexer of ALL created caches was unregistered, not just of the ones from the cache manager being shut down. In my case the two (differently named) cache managers were sharing the same jmx domain (contrary to what I said in description - I was confused). 

It turns out the problem is the object name of the MassIndexer (and possibly some other components??) does not contain the cache manager name as an attribute. The usual naming scheme for cache components is: {{jmxDomain + ":type=" + aType + ",manager=" + ObjectName.quote(cacheManagerName) + ",name=" + ObjectName.quote(cacheName) + ",component=" + aComponentName}}, but for the MassIndexer the cache manager name part is missing, so the wildcard MBean query used for unregistering (in org.infinispan.query.impl.LifecycleManager.cacheStopping()) matches a bit more instances than intended.

So, should we close this as invalid and create a new issue for the newly described case?
                
      was (Author: anistor):
    I've revisited this issue and found that my initial analysis was completely wrong, the title and description are completely inaccurate, but there still is an issue here with the unregistering of MBeans during cache stop; a bit different one though.

First of all, the problem I noticed initially was the MassIndexer MBean disappearing from the MBean server if there were two cache managers and one of them was shut down at some point. My problem was that the MassIndexer of ALL created caches was unregistered, not just of the ones from the cache manager being shut down. In my case the two (differently named) cache managers were sharing the same jmx domain (contrary to what I said in description - I was confused). 

It turns out the problem is the object name of the MassIndexer (and possibly some other components??) does not contain the cache manager name as an attribute. The usual naming scheme for cache components is: ```jmxDomain + ":type=" + aType + ",manager=" + ObjectName.quote(cacheManagerName) + ",name=" + ObjectName.quote(cacheName) + ",component=" + aComponentName```, but for the MassIndexer the cache manager name part is missing, so the wildcard MBean query used for unregistering (in org.infinispan.query.impl.LifecycleManager.cacheStopping()) matches a bit more instances than intended.

So, should we close this as invalid and create a new issue for the newly described case?
                  
> LifecycleManager of query module keeps references to per cache manager resources (jmx related)
> ----------------------------------------------------------------------------------------------
>
>                 Key: ISPN-3531
>                 URL: https://issues.jboss.org/browse/ISPN-3531
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Querying
>    Affects Versions: 6.0.0.Alpha4
>            Reporter: Adrian Nistor
>            Assignee: Adrian Nistor
>              Labels: 620
>             Fix For: 6.0.0.Final
>
>
> 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.

--
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