You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Daniel Müller (JIRA)" <ji...@apache.org> on 2013/04/24 16:13:17 UTC

[jira] [Created] (ARIES-1056) Can't access MBeans by using the specified object name constants

Daniel Müller created ARIES-1056:
------------------------------------

             Summary: Can't access MBeans by using the specified object name constants
                 Key: ARIES-1056
                 URL: https://issues.apache.org/jira/browse/ARIES-1056
             Project: Aries
          Issue Type: Bug
          Components: JMX
            Reporter: Daniel Müller


I've updated org.apache.aries.jmx.api from 1.0.0 to 1.1.0 and figured out, that by calling

final BundleStateMBean bundleStateMBean = JMX.newMBeanProxy(msc, new ObjectName(BundleStateMBean.OBJECTNAME), BundleStateMBean.class);
final TabularData tabularData = bundleStateMBean.listBundles();

an InstanceNotFoundException is thrown due to the fact that osgi.core:type=bundleState,version=1.7 is not available. The code snippet above has already worked with version 1.0.0!

I've found out that, if I use

final BundleStateMBean bundleStateMBean = JMX.newMBeanProxy(msc, new ObjectName("osgi.core:type=framework,version=1.7,framework=org.apache.felix.framework,uuid=62b24e2d-d077-4d6e-b44a-ab98fe352e88"), BundleStateMBean.class);
final TabularData tabularData = bundleStateMBean.listBundles();

everything works fine. But only as long as the UUID of the MBean doesn't change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira