You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2014/06/26 20:09:24 UTC

[jira] [Resolved] (CAMEL-7546) Avoid clash of CamelContext managementName in OSGi

     [ https://issues.apache.org/jira/browse/CAMEL-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-7546.
--------------------------------

    Resolution: Fixed

> Avoid clash of CamelContext managementName in OSGi
> --------------------------------------------------
>
>                 Key: CAMEL-7546
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7546
>             Project: Camel
>          Issue Type: Bug
>          Components: osgi
>    Affects Versions: 2.13.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.13.2, 2.14.0
>
>
> There can be a potential clash in OSGi when there are 2+ camelContext in the same bundle, as they will by default reuse the same managementName in the mbean naming, where it uses the symbolic name of the OSGi bundle.
> We should detect this clash and use the counter to make it unique.
> This is part of CAMEL-6972



--
This message was sent by Atlassian JIRA
(v6.2#6252)