[infinispan-issues] [JBoss JIRA] (ISPN-10887) GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently

[Nistor Adrian (Jira)]

     [ https://issues.redhat.com/browse/ISPN-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nistor Adrian updated ISPN-10887:
---------------------------------
    Fix Version/s: 10.1.0.Beta1
                       (was: 10.1.0.CR1)


> GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-10887
>                 URL: https://issues.redhat.com/browse/ISPN-10887
>             Project: Infinispan
>          Issue Type: Bug
>          Components: JMX, reporting and management
>    Affects Versions: 10.0.0.Final
>            Reporter: Nistor Adrian
>            Assignee: Nistor Adrian
>            Priority: Major
>             Fix For: 10.1.0.Beta1
>
>
> The feature is supposed to allow detection of an already occupied jmx domain and generate a new unique one by adding an increasing number suffix. The implementation polls the MBeanServer registry using queryNames until a free domain is found. The unique domain generation and the registration of the first MBean to occupy it is not atomic, so multiple CacheManagers starting up concurrently can mistakenly pick up the same domain.
> This can be fixed by making it atomic, by not using queryNames and instead directly registering the first bean, retrying if InstanceAlreadyExistsException. The first bean has to be picked identically by all cache managers. We'll pick first the cache manager itself and register the other components afterwards.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)