Hi 

Sorry my bad it used to be a WARN I think, but I can see it's thrown.
I will relax it to a DEBUG message with a hint that this is okay and Camel will 
continue.

Med venlig hilsen
 
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk

-----Original Message-----
From: Claus Ibsen [mailto:[EMAIL PROTECTED] 
Sent: 17. juli 2008 10:25
To: [email protected]
Subject: RE: How can avoid to have such error message 
"instanceAllreadyExistsException" ?

Hi

It's not an ERROR it's a WARN. Camel will work fine.

As it's the same JMS queue we can not create 3 different mbeans for it in the 
JMX tree. We had an issue before where each of them will get their own instance 
number 0, 1, 2 etc. But as you write it's the same endpoint.

Maybe the WARN logging is to aggressive and should just be DEBUG and without 
the stacktrace - it's of no use. 

Let me take a look.


Med venlig hilsen
 
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk

-----Original Message-----
From: cmoulliard [mailto:[EMAIL PROTECTED] 
Sent: 17. juli 2008 10:14
To: [email protected]
Subject: How can avoid to have such error message 
"instanceAllreadyExistsException" ?


Hi,

I have created different routes hosted in two different packages.

Package : com.myApplication.routing.in
Class : RouteA
Class : RouteB
...

Package : com.myApplication.routing.out
Class : RouteC

In the RouteB and RouteC, we have a common endpoint which is
"activemq:queue:myqueue".

During the launch of Camel, I have the following error :

        <camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring";>
                <package>com.myapplication.routing.in</package>
                <package>com.myapplication.routing.out</package>
        </camelContext>

43javax.management.InstanceAlreadyExistsException:
org.apache.camel:context=dell-charles/camel,[EMAIL PROTECTED],type=route,[EMAIL 
PROTECTED]
        at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(Unknown Source)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(Unknown
Source)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(Unknown
Source)
        at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(Unknown
Source)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(Unknown Source)

How to solve this ?

Regards,

Charles  Moulliard


-----
Enterprise Architect

Xpectis
12, route d'Esch
L-1470 Luxembourg

Phone +352 25 10 70 470
Mobile +352 621 45 36 22

e-mail : [EMAIL PROTECTED]
web site : www.xpectis.com 
-- 
View this message in context: 
http://www.nabble.com/How-can-avoid-to-have-such-error-message-%22instanceAllreadyExistsException%22---tp18503700s22882p18503700.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to