camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3031) Auto assigned CamelContext id should be unique in the JVM
Date Wed, 11 Aug 2010 02:57:47 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61148#action_61148
] 

Willem Jiang commented on CAMEL-3031:
-------------------------------------

@Claus,

I just didn't some test about camelContext name within the OSGi container,  I don't find the
issue of static atomic counter which causes all the camel id end up with camel-1.
But I agree to add the bundle id in to the camelContext which will help user to find their
camel context easily.



> 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.


Mime
View raw message