Return-Path: 
 <dev-return-23121-apmail-camel-dev-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-dev-archive@www.apache.org
Received: (qmail 87962 invoked from network); 10 Nov 2010 12:54:12 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 10 Nov 2010 12:54:12 -0000
Received: (qmail 6258 invoked by uid 500); 10 Nov 2010 12:54:44 -0000
Delivered-To: apmail-camel-dev-archive@camel.apache.org
Received: (qmail 6097 invoked by uid 500); 10 Nov 2010 12:54:41 -0000
Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@camel.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@camel.apache.org>
List-Post: <mailto:dev@camel.apache.org>
List-Id: <dev.camel.apache.org>
Reply-To: dev@camel.apache.org
Delivered-To: mailing list dev@camel.apache.org
Received: (qmail 6089 invoked by uid 500); 10 Nov 2010 12:54:40 -0000
Delivered-To: apmail-activemq-camel-dev@activemq.apache.org
Received: (qmail 6086 invoked by uid 99); 10 Nov 2010 12:54:40 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Nov 2010 12:54:40 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Nov 2010 12:54:40 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAACsJxJ000915
	for <camel-dev@activemq.apache.org>; Wed, 10 Nov 2010 12:54:19 GMT
Message-ID: <28981962.111289393659741.JavaMail.jira@thor>
Date: Wed, 10 Nov 2010 07:54:19 -0500 (EST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-3324) Camel should auto find free
 CamelContext MBean name when registering Camel in JMX to avoid failing on
 startup due existing mbean name
In-Reply-To: <21163927.81289389699573.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c


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

Claus Ibsen resolved CAMEL-3324.
--------------------------------

    Resolution: Fixed

trunk: 1033440.

> Camel should auto find free CamelContext MBean name when registering Camel in JMX to avoid failing on startup due existing mbean name
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3324
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3324
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: osgi
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>
> This makes it much easier when running multiple Camel applications in the same JVM. You may have assigned a duplicate name in the CamelContext but in different WARs / bundles etc. Then previously Camel would not be able to start the 2nd application as the 1st had already taking the MBean name.
> Instead Camel should auto remedy this by computing a free name to use instead.
> For example
> WAR-a
> {code:xml}
> <camelContext id="foo">
> ...
> </camelContext>
> {code}
> WAR-b
> {code:xml}
> <camelContext id="foo">
> ...
> </camelContext>
> {code}
> Now what happens is that
> {code}
> WAR-a : DEBUG Registered MBean with objectname: org.apache.camel:context=localhost/foo,type=context,name="foo"
> ...
> WAR-b: WARN This CamelContext(foo) will be registered using the name: foo-2 due to clash with an existing name already registered in MBeanServer.
> WAR-b DEBUG Registered MBean with objectname: org.apache.camel:context=localhost/foo-2,type=context,name="foo"
> {code}
> As you can see WAR-b has the MBean name reassigned to foo-2 to avoid the clash.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.