Infinispan 8.1.2 There's already a JMX MBean instance type=Cache,name="__cluster_registry_cache__(repl_sync)

[franco80]

Hi all

i tryied to stop the cache manager like this: CACHE_MANAGER.stop(), but still i can't do this without errors:

Caused by: org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=Cache,name="__cluster_registry_cache__(repl_sync)",manager="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

I found this [ISPN-4659] DefaultCacheManager.stop() is not removing the GlobalComponentRegistry JMX domain - JBoss Issue Tracker but it's not solved.

I don't want to use option "allowDuplicateDomains", becouse i want to have only one, but i need to use jenkins to redeploy our application. I did unregistering all mbeans from JMX but after redeploy takes too much memmory each time doing this and during redepliy i recive OutOfMemmory error. Later also I added simply removing all caches from cache manager (with unregistering mbeans) with stopping cache manager and it's working fine but can you tell me what is good approach ?

What is working actually is:

CACHE_MANAGER.removeCache(someCacheName);

CACHE_MANAGER.removeCache("__cluster_registry_cache__(repl_sync)");

unregisterMBean();

CACHE_MANAGER.stop();

can you please advise what approach should be used to redeploy application ?

[sebastian.laskawiec]

Could you please tell us more about they way you are deploying your application? I'm assuming you use an Application Server (a Wildfly instance?). It might be also important which libraries are packed into your deployment.

It might be possible that you encounter some error with our CDI integration bits (if they are enabled, our extension tries to inject Cache instances where needed). You might find some blogs describing how does work:

• http://blog.infinispan.org/2014/09/cache-and-cache-manger-events-in-cdi.html
• http://blog.infinispan.org/2011/09/when-infinispan-meets-cdi.html

[franco80]

ejb service as a singleton with startup annotation, wildfly 8.2.1 standalone instance

[dan.berindei]

Looks like you're hitting [ISPN-4659] DefaultCacheManager.stop() is not removing the GlobalComponentRegistry JMX domain, indeed. It was fixed in Infinispan 8.2.0.Final, but your workaround should also be fine if you can't upgrade.

Note that removeCache(someCacheName) will remove the cache on all the cluster nodes, if the cache manager is clustered. It's also not necessary, the cache manager handles regular caches properly. So this workaround should be more correct:

CACHE_MANAGER.getCache("__cluster_registry_cache__(repl_sync)").stop();

unregisterMBean();

CACHE_MANAGER.stop();

[franco80]

ok, it looks good, i'll try to upgrade Infinispan to 8.2 in this case for our cluster (replicatated cache), we're starting to use Wildfly 10 (there is Infinispan 8.1) slowly and I think it should be possible without major problems. Also I'll try to stop the cache manager like you mentioned: CACHE_MANAGER.getCache("__cluster_registry_cache__(repl_sync)").stop();

thanks a lot