[infinispan-issues] [JBoss JIRA] (ISPN-2290) MBeans should be registered even if JMX statistics gathering is disabled

Galder Zamarreño (JIRA) jira-events at lists.jboss.org
Mon Sep 17 13:52:34 EDT 2012


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

Galder Zamarreño commented on ISPN-2290:
----------------------------------------

On top of the changes required to use the right configuration, I think there's a JMX leak somewhere, cos I'm seeing a lot of:

{code}Caused by: org.infinispan.jmx.JmxDomainConflictException: Domain already registered infinispan2 when trying to register: type=Cache,name="___defaultcache(local)",manager="DefaultCacheManager"{code}

Funnily enough, it only happens when you run the testsuite of more than one component in succession. Since we don't fork, if the mbean server is not cleaned up when the cache stops, the next one that uses the same jmx domain will fail. However, that will only happen when the other component's testsuite starts up, cos TestCacheManagerFactory.jmxDomainPostfix will start from 1 again.

So Manik, not as trivial as you thought ;)
                
> MBeans should be registered even if JMX statistics gathering is disabled
> ------------------------------------------------------------------------
>
>                 Key: ISPN-2290
>                 URL: https://issues.jboss.org/browse/ISPN-2290
>             Project: Infinispan
>          Issue Type: Bug
>          Components: JMX, reporting and management
>    Affects Versions: 5.1.7.Final
>            Reporter: Manik Surtani
>            Assignee: Manik Surtani
>             Fix For: 5.2.0.Alpha4, 5.2.0.Final
>
>
> JMX MBeans should still be registered with an MBean server even if statistics gathering is disabled, to allow for operations on a running grid.  If an MBean server is not available though, this should be short-circuited.

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



More information about the infinispan-issues mailing list