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)