[jira] [Created] (CAMEL-11002) Camel-Blueprint - failed container fails to remove JMX object

["Paolo Antinori (JIRA)" <ji...@apache.org>]

Paolo Antinori created CAMEL-11002:
--------------------------------------

             Summary: Camel-Blueprint - failed container fails to remove JMX object
                 Key: CAMEL-11002
                 URL: https://issues.apache.org/jira/browse/CAMEL-11002
             Project: Camel
          Issue Type: Bug
          Components: camel-blueprint
    Affects Versions: 2.18.2
            Reporter: Paolo Antinori
            Assignee: Andrea Cosentino


There is an issue with {{camel-blueprint}} lifecycle, similar to issue CAMEL-10411.

In case of an issue with an endpoint configuration, like for instance a non existing http endpoint {{uri="http://localhost:6000/"}}, the JMX object of the CamelContext, remains registered, even if it shouldn't.

Camel current code actually already unregisters it, in {{org.apache.camel.management.DefaultManagementLifecycleStrategy#onContextStop}}, triggered by {{org.apache.camel.support.ServiceSupport#start}} exception handling section.

The reason why the MBean object stays registered, is because of {{BlueprintCamelContext}} is still registered as an OSGi service listener, and {{org.apache.camel.blueprint.BlueprintCamelContext#serviceChanged}}  is invoked, re-registering a new instance.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)