[infinispan-issues] [JBoss JIRA] (ISPN-2886) Using multiple DefaultCacheManager w/o jmx leads to JmxDomainConflictException
Galder Zamarreño (JIRA)
issues at jboss.org
Fri Jan 30 08:31:49 EST 2015
[ https://issues.jboss.org/browse/ISPN-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreño updated ISPN-2886:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.1.0.Final
Resolution: Done
> Using multiple DefaultCacheManager w/o jmx leads to JmxDomainConflictException
> ------------------------------------------------------------------------------
>
> Key: ISPN-2886
> URL: https://issues.jboss.org/browse/ISPN-2886
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 5.2.1.Final, 6.0.2.Final, 7.1.0.CR2
> Reporter: Thomas Fromm
> Assignee: Sebastian Łaskawiec
> Priority: Minor
> Fix For: 7.1.0.Final
>
>
> Creating multiple instances of DefaultCacheManager leads to CacheManagerJmxRegistrationTest, even when JMX is disabled in configuration.
> org.infinispan.jmx.JmxDomainConflictException: Domain already registered org.infinispan when trying to register: type=CacheManager,name="DefaultCacheManager"
> at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:75)
> at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:101)
> at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:95)
> at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:59)
> at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:63)
> at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:705)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:300)
> at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:171)
> h2. Update
> This also happens when using CDI Extension in Library mode with Wildfly. Attached Pull Request fixes that case.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the infinispan-issues
mailing list