[
https://issues.apache.org/activemq/browse/CAMEL-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61092#action_61092
]
Ashwin Karpe commented on CAMEL-3031:
-------------------------------------
Hi Claus,
Ben and I are working on the same customer project where we ran into this
issue. The version of Camel that the customer is using is Camel version 2.2.
The deployment is on a FUSE OSGi container version 4.2.0
Hope this helps.
Cheers,
Ashwin...
> 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.
