Why is JMX gone after upgrading to Camel 2.18.x?

2017-07-11 Thread Henrik Brautaset Aronsen
I am trying to upgrade to Camel 2.18.3 (from 2.17.3), and now JMX doesn't seem to work. camelContext.getManagedCamelContext() returns null, and so does getManagementName(). I can't find any interesting in the logs, and am at loss regarding how to debug this. Any ideas? A git bisect shows https:/

Re: Why is JMX gone after upgrading to Camel 2.18.x?

2017-07-11 Thread Claus Ibsen
Hi You need to tell more about how you run Camel. And how you upgraded. On Tue, Jul 11, 2017 at 11:35 AM, Henrik Brautaset Aronsen wrote: > I am trying to upgrade to Camel 2.18.3 (from 2.17.3), and now JMX doesn't > seem to work. > > camelContext.getManagedCamelContext() returns null, and so doe

Re: Why is JMX gone after upgrading to Camel 2.18.x?

2017-07-11 Thread Henrik B A
On Jul 11, 2017; 11:51am Claus Ibsen wrote: > Hi > > You need to tell more about how you run Camel. And how you upgraded. I use Spring: @Configuration public class PaleConfig extends CamelConfiguration { camelContext.setUseMDCLogging(false); camelContext.setStreamCaching(true); camelContex

Re: Why is JMX gone after upgrading to Camel 2.18.x?

2017-07-11 Thread Henrik B A
Typo, the PaleConfig class should obviously be like this: @Configuration public class PaleConfig extends CamelConfiguration { @Override protected void setupCamelContext(CamelContext camelContext) { camelContext.setUseMDCLogging(false); camelContext.setStreamCaching(true); camelContex

Re: Why is JMX gone after upgrading to Camel 2.18.x?

2017-07-11 Thread Henrik Brautaset Aronsen
Hi Claus. I've added an example project at https://github.com/henrik242/camel218jmx SomeTest shows how camelContext.getManagementName() is null (in 2.18.x, but not 2.17.7) when fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a Bean. If I have an Autowired camelContext