You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Jeremie Granat (JIRA)" <ji...@apache.org> on 2008/07/04 10:19:31 UTC

[jira] Created: (FELIX-623) JMood Restart Problem

JMood Restart Problem
---------------------

                 Key: FELIX-623
                 URL: https://issues.apache.org/jira/browse/FELIX-623
             Project: Felix
          Issue Type: Bug
            Reporter: Jeremie Granat
            Priority: Minor


I try to first test the resolvability of the configuration before using it. To do this, the bundles of the configurations are installed and the status is queried. If all the bundles are resolved by the framework, the bundles are deinstalled and reinstalled again in the same order. The JMood bundles seems to have a problem with such a method. After reinstalling the bundle, an exception is thrown while starting it again.
org.osgi.framework.BundleException: 
    Exception in org.apache.felix.jmood.Activator.start() 
    of bundle org.apache.felix.org.apache.felix.jmood.
Caused by: javax.management.InstanceAlreadyExistsException: 
    osgi.core:type=controller

It seems that the JMood bundle does not unregister its MBean instances from the MBean repository it creates in the background at first start-up. The correct
behavior should be to remove the managed instances from the registry when the bundle is deinstalled. If JMood is responsible for the registry, it should also
stop it. 


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