camel-context jmx entries or mbean is not removed from bundle having misconfigured endpoints is uninstalled
Issue
- I want to define a managementNamePattern like this:
<camelContext id="monitoring-pms-event-manager" managementNamePattern="#camelId#" >
- however when i do subsequent installs, i get this error:
2016-08-15 12:52:46,163 WARN (Karaf Shell Console Thread) [org.apache.camel.blueprint.BlueprintCamelContext] : Lifecycle strategy vetoed starting CamelContext (monitoring-pms-event-manager) due CamelContext (monitoring-pms-event-manager) with ObjectName[org.apache.camel:context=monitoring-pms-event-manager,type=context,name="monitoring-pms-event-manager"] is already registered. Make sure to use unique names on CamelContext when using multiple CamelContexts in the same MBeanServer.
- One of the endpoint in route is configured following way. Note 'foo=bar' option which is not a correct configuration. While developing application if we misconfigure something by mistake, we are not able to uninstall application properly. This is annoying.
file://c:/temp/data/monitoring/pms/event-manager/loader/input?delay=20000&filter=%23cleanAntFilter&foo=bar&initialDelay=10000&noop=true&recursive=true
- when i check the JMX console, i can see that the previous bundle's camel context JMX Object bean hasnt been removed even after its been uninstalled.
Environment
- Red Hat JBoss Fuse
- 6.2.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
