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 2.1 timeframe. On Wed, May 13, 2009 at 6:43 PM, Siegfried.Wirth <[email protected]> wrote: > > 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 context is really > startet/initialized. > > We couldn´t figure out how the contexts are startet and endpoint are created > and how the correct relation between endpoints and contexts is assured. > > > Claus Ibsen-2 wrote: >> >> 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. >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> Apache Camel Reference Card: >> http://refcardz.dzone.com/refcardz/enterprise-integration >> Interview with me: >> http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress >> >> > > -- > View this message in context: > http://www.nabble.com/Two-camel-contexts-and-assinging-endpoints-%28visible-by-jconsole%2C-jmx%29-tp23520282p23525607.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
