[CAMEL-11002] Camel-Blueprint - failed container fails to remove JMX object

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.18.2
• Fix Version/s: 2.18.4, 2.19.0
• Component/s: camel-blueprint
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• External issue ID: https://issues.jboss.org/browse/ENTESB-6431
• Assignee: Andrea Cosentino
• Reporter: Paolo Antinori
• Created: 13/Mar/17 12:20
• Updated: 13/Mar/17 12:51
• Resolved: 13/Mar/17 12:51

Description

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.

Issue Links

• links to: GitHub Pull Request #1531