Details
-
Bug
-
Resolution: Done
-
Critical
-
7.2.1.Final
-
None
Description
ConfigurationOverrideTest uses the default global configuration, and it fails when another test has already registered a cache manager MBean in JMX with the same name:
org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element
at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:51)
at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79)
at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73)
at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37)
at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41)
at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:625)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:218)
at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:199)
at org.infinispan.configuration.ConfigurationOverrideTest.testOverrideWithStore(ConfigurationOverrideTest.java:80)
We should verify the other tests as well, to make sure they all use the PerThreadMBeanServerLookup and/or a unique JMX domain.
Attachments
Issue Links
- is incorporated by
-
-
- Closed
-