If we have misconfigured endpoint than mbean is not removed after bundle uninstall.

Extract reproducer 01684771_mbeanNotRemoved.zip. Unzip it. There is a workaround, check description section. 1. Set uri of endpoint with id "globalscape-clean" to your local path. 2. If you see currently endpoint for camel's file component is set with wrong option( Note: 'bar=foo' at the end of uri). <endpoint id= "globalscape-clean" uri= "file: //home/cpandey/NotBackedUp/Downloads/quart2Poll?recursive= true &amp;filter=#cleanAntFilter&amp;noop= true &amp;initialDelay=1000&amp;delay=5000&amp;bar=foo" /> 3. Build using `mvn clean install -DskipTests`. 4. Deploy this using command osgi:install -s mvn:com.mycompany/camelcontext-error/1.0.0-SNAPSHOT 5. We get error in logs, which is obvious as we are using wrong option for file endpoint. Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: file: //home/cpandey/NotBackedUp/Downloads/quart2Poll?bar=foo&delay=5000&filter=%23cleanAntFilter&initialDelay=1000&noop= true &recursive= true due to: There are 1 parameters that couldn't be set on the endpoint. Check the uri if the parameters are spelt correctly and that they are properties of the endpoint. Unknown parameters=[{bar=foo}] 6. Now uninstall this application. uninstall <bundle_id> 7. Now remove "&bar=foo" from uri option of file endpoint. This is now correct configurations. Build the project again using command `mvn clean install -DskipTests`. 8. Deploy again using command `osgi:install -s mvn:com.mycompany/camelcontext-error/1.0.0-SNAPSHOT`. 9. It finally results in error: 10:29:22,830 | WARN | l Console Thread | BlueprintCamelContext | 198 - org.apache.camel.camel-core - 2.15.1.redhat-621084 | Lifecycle strategy vetoed starting CamelContext (camelcontext-error123) due CamelContext (camelcontext-error123) with ObjectName[org.apache.camel:context=camelcontext-error123,type=context,name= "camelcontext-error123" ] is already registered. Make sure to use unique names on CamelContext when using multiple CamelContexts in the same MBeanServer. 10:29:22,830 | ERROR | l Console Thread | BlueprintCamelContext | 204 - org.apache.camel.camel-blueprint - 2.15.1.redhat-621084 | Error occurred during starting Camel: CamelContext(camelcontext-error123) due CamelContext (camelcontext-error123) with ObjectName[org.apache.camel:context=camelcontext-error123,type=context,name= "camelcontext-error123" ] is already registered. Make sure to use unique names on CamelContext when using multiple CamelContexts in the same MBeanServer. org.apache.camel.VetoCamelContextStartException: CamelContext (camelcontext-error123) with ObjectName[org.apache.camel:context=camelcontext-error123,type=context,name= "camelcontext-error123" ] is already registered. Make sure to use unique names on CamelContext when using multiple CamelContexts in the same MBeanServer. at org.apache.camel.management.DefaultManagementLifecycleStrategy.onContextStart(DefaultManagementLifecycleStrategy.java:173) at org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:2552) at org.apache.camel.impl.DefaultCamelContext.access$000(DefaultCamelContext.java:167) at org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2467) at org.apache.camel.impl.DefaultCamelContext$2.call(DefaultCamelContext.java:2463)