camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen">
Subject RE: any reason we don't use the platform MBeanServer by default?
Date Tue, 29 Jul 2008 13:38:39 GMT

Med venlig hilsen
Claus Ibsen
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576

-----Original Message-----
From: James Strachan [] 
Sent: 29. juli 2008 15:35
Subject: Re: any reason we don't use the platform MBeanServer by default?

Agreed. I'm +1 on using it by default unless anyone else can think of
a good reason why not.

i.e. the default behaviour of running camel should be IMHO that JMX is
enabled by default and that you can connect using JConsole and see the
JVM and camel mbeans :)

2008/7/29 William Tam <>:
> The pflatform mbean server option was introduced in 1.4. It is mainly
> for back compatibility reason that it wasn't the default.  I agree
> that it should be the default.. That can eliminate creating a mbean
> server instance for camel.  It also makes it easier to use websphere
> as you have to either use platfform mbean server or change the domain
> name to match theirs.
> On Tue, Jul 29, 2008 at 6:07 AM, James Strachan
> <> wrote:
>> When running Camel in the eclipse plugin I was scratching my head a
>> bit trying to figure out why the MBeans were not visible in the JMX
>> console. From noodling the code in
>> DefaultInstrumentationAgent.findOrCreateMBeanServer() it looks like we
>> don't use the platform mbean server by default unless the user
>> specifies the system property...
>> -Dorg.apache.camel.jmx.usePlatformMBeanServer=true
>> I just kinda thought that was a bit backwards; shouldn't we use the
>> platform mbean server by default - then using JConsole we can actually
>> see the mbeans? Is there some reason we didn't enable this by default?
>> --
>> James
>> -------
>> Open Source Integration


Open Source Integration

View raw message