Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.218.226 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=poO4y2shSEEIhr6SWje3d0+OVlTdjwju5RCdn9PynqJDUV8UG4j5pb/qb4ielw+Vds
         Mi/XX8ApT1kYCRCeCRVQ+g1vD+1QlcZ1lGfrO3k94/6tHDfyj0XWHnX8WHChU1GF7eq8
         szIzpljy776rlSgMlwAQGDcbe+EP4NlJ8N02k=
MIME-Version: 1.0
In-Reply-To: <23525607.post@talk.nabble.com>
References: <23520282.post@talk.nabble.com>
 <5380c69c0905130553p17ba02c5q816fe97d7eeda422@mail.gmail.com>
	<23525607.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sat, 16 May 2009 16:59:00 +0200
Message-ID: <5380c69c0905160759w49d807ddj75acd285e3f9f551@mail.gmail.com>
Subject: Re: Two camel contexts and assinging endpoints (visible by jconsole,
	jmx)
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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
<siegfried.wirth@capgemini-sdm.com> 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 a=
re
> added to the InstrumentationLifecyleStrategy before the context is really
> startet/initialized.
>
> We couldn=B4t figure out how the contexts are startet and endpoint are cr=
eated
> 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=3D78=
93-progress
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Two-camel-contexts-an=
d-assinging-endpoints-%28visible-by-jconsole%2C-jmx%29-tp23520282p23525607.=
html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>


--=20
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus