[
https://issues.apache.org/jira/browse/ARIES-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847152#action_12847152
]
Thomas Diesler commented on ARIES-259:
--------------------------------------
This also pertains to ServiceState and generally to any uncought Exception in
the JMXAgent.unregisterBeans(MBeanServer server) loop.
BTW, why is the MBean register/unregister work been done asynchronously. this
makes my remote osgi testsuite that delegates to JMX much more complicated.
> MBeans not getting unregistered reliably
> ----------------------------------------
>
> Key: ARIES-259
> URL: https://issues.apache.org/jira/browse/ARIES-259
> Project: Aries
> Issue Type: Bug
> Components: JMX
> Reporter: Thomas Diesler
> Attachments: ARIES-259-20100318.patch
>
>
> Closing the MBeanServiceTracker asyncronously triggers
> JMXAgent.unregisterBeans(MBeanServer server)
> If there is a unexpected exception while unregistering an MBeanHandler the
> ones coming after it will not get unregitered.
> In particular I am seeing an unguarded postDeregister hook.
> Caused by: java.lang.IllegalStateException: Invalid BundleContext.
> at
> org.apache.felix.framework.BundleContextImpl.checkValidity(BundleContextImpl.java:393)
> at
> org.apache.felix.framework.BundleContextImpl.removeBundleListener(BundleContextImpl.java:170)
> at
> org.apache.aries.jmx.framework.BundleState.shutDownDispatcher(BundleState.java:353)
> at
> org.apache.aries.jmx.framework.BundleState.postDeregister(BundleState.java:293)
> at
> org.apache.aries.jmx.framework.RegistrableStandardEmitterMBean.postDeregister(RegistrableStandardEmitterMBean.java:69)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postDeregisterInvoke(DefaultMBeanServerInterceptor.java:1065)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
