Hi
Thanks for reporting.
JMX is planned for an overhaul in Camel 2.1 so I have targeted your
issue for Camel 2.1.
Yes the current JMX instrumentation code is a bit complex as its kinda
like 2 phased:
registering mbeans and then linking to the Camel model.
All together its being address in Camel
Hi Claus,
I created a JIRA Ticket
https://issues.apache.org/activemq/browse/CAMEL-1612.
Although we detected the issue using JMX we think the underlying problem
could be more general. It looks like the endpoints of one camel context are
added to the InstrumentationLifecyleStrategy before the con
Hi
Just a quite note.
A total overhaul / rewrite of the JMX stuff is planned for Camel 2.1.
You are welcome to create a ticket in JIRA and if possible attach a
small demo app that demonstrates the problem.
Maybe we can do something for 2.0 but the real effort is planned for 2.1.
On Wed, May 13
Hi,
we are trying to use two camel contexts with JMX. It seems to us that the
endpoints are not correctly registered - in fact it looks like the contexts
are mixed up. We debugged up to InstrumentationLifecycleStrategy, where it
looks like that starting the contexts and registering the endpoints
