[IGNITE-7398] InstanceNotFoundException appears in the log when a cache is closed and MBeans are disabled

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.5
• Assignee: Pavel Vinokurov
• Reporter: Stanislav Lukyanov
• Created: 12/Jan/18 13:21
• Updated: 26/Feb/18 12:54
• Resolved: 26/Feb/18 12:52

Description

If IGNITE_MBEANS_DISABLED is set to true, whenever a cache is started the following error is logged:
javax.management.InstanceNotFoundException: org.apache:clsLdr=18b4aac2,igniteInstanceName=mbeans.GridMBeanDisableSelfTest0,group=Cache groups,name=MyCache
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415)
at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546)
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.cleanup(GridCacheProcessor.java:606)
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2264)
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCacheGroup(GridCacheProcessor.java:2253)
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:907)
at org.apache.ignite.internal.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:872)
at org.apache.ignite.internal.IgniteKernal.stop0(IgniteKernal.java:2316)
at org.apache.ignite.internal.IgniteKernal.stop(IgniteKernal.java:2182)
at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2512)
at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2475)
at org.apache.ignite.internal.IgnitionEx.stop(IgnitionEx.java:362)
at org.apache.ignite.Ignition.stop(Ignition.java:224)
at org.apache.ignite.internal.IgniteKernal.close(IgniteKernal.java:3509)
at org.apache.ignite.util.mbeans.GridMBeanDisableSelfTest.testCorrectMBeanInfo(GridMBeanDisableSelfTest.java:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
at org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
at org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
at java.lang.Thread.run(Thread.java:748)

That's because GridCacheProcessor::cleanup unconditionally attempts to unregister cache's MBean, not checking whether or not the cache actually has an MBean registered for it.

Issue Links

• links to: GitHub Pull Request #3492