You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Adam Wojtuniak (JIRA)" <ji...@apache.org> on 2010/03/19 18:46:28 UTC

[jira] Assigned: (ARIES-260) Reconsider synchronous MBean registration/unregistration

     [ https://issues.apache.org/jira/browse/ARIES-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Wojtuniak reassigned ARIES-260:
------------------------------------

    Assignee: Adam Wojtuniak

> Reconsider synchronous MBean registration/unregistration
> --------------------------------------------------------
>
>                 Key: ARIES-260
>                 URL: https://issues.apache.org/jira/browse/ARIES-260
>             Project: Aries
>          Issue Type: Bug
>          Components: JMX
>            Reporter: Thomas Diesler
>            Assignee: Adam Wojtuniak
>
> Currently if you do 
> Bundle bundle = context.installBundle("org.apache.aries.jmx.jar");
> bundle.start()
> BundleStateMBean mbean = MBeanProxy.get(server, objectName, BundleStateMBean.class);
> mbean.listBundles();
> This might fail because the MBeans may not be registered when  bundle.start() returns. 
> To compensate this effect a client will have to do some server.isRegistered/timeout logic or perhaps some  more complicated notification logic.
> IMHO, MBean registration should not be treated differently to osgi service registration i.e. it should be complete when Bundle.start() returns.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.