I created an issue for this: https://issues.apache.org/jira/browse/CAMEL-11536
Henrik On Tue, Jul 11, 2017 at 4:03 PM, Henrik Brautaset Aronsen < henrik.aron...@gmail.com> wrote: > 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 in the test, then getManagementName() > returns the proper name. > > Cheers, > Henrik > > > On Tue, Jul 11, 2017 at 11:51 AM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > >> 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 >> <henrik.aron...@gmail.com> 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 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://github.com/apache/camel/commit/1a4e34960fb6953bb8047 >> 17a728c294f27108a4f >> > as the offending commit, but I can't see why it creates trouble. >> > >> > cheers, >> > Henrik >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > >
