[
https://issues.apache.org/activemq/browse/CAMEL-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61149#action_61149
]
Willem Jiang commented on CAMEL-3031:
-------------------------------------
I just found there are something wrong with the CamelContextFactoryBean's
createCamelContext.
It will set the camelcontext id with id name which could be an implicit one,
and it will override the OsgiCamelContextNameStratgy which an
ExplicitCamelContextNameStratgy.
So I made some change in the trunk: 984294
> Auto assigned CamelContext id should be unique in the JVM
> ---------------------------------------------------------
>
> Key: CAMEL-3031
> URL: https://issues.apache.org/activemq/browse/CAMEL-3031
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.5.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/multiple-camel-contexts-as-viewed-from-JMX-tp2265902p2265902.html
> Route ids are being unique, so we should be able to do that for CamelContext
> id as well. And we should reject starting an application if an existing
> CamelContext exists with the same id. This applies to JMX.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
