[
https://issues.apache.org/jira/browse/CAMEL-11536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henrik updated CAMEL-11536:
---------------------------
Regression: Regression
> camelContext.getManagedCamelContext returns null in 2.18+
> ---------------------------------------------------------
>
> Key: CAMEL-11536
> URL: https://issues.apache.org/jira/browse/CAMEL-11536
> Project: Camel
> Issue Type: Bug
> Components: camel-jmx
> Affects Versions: 2.18.0, 2.18.1, 2.18.2, 2.18.3, 2.18.4, 2.19.0, 2.19.1
> Reporter: Henrik
>
> I have created an example project at https://github.com/henrik242/camel218jmx
> that shows the problem:
> SomeTest shows how camelContext.getManagementName() is null in 2.18.x when
> fetched in InitizializingBean.afterPropertiesSet(), and when delivered from a
> Bean. 2.17.7 does not have this problem.
> If I have an Autowired camelContext in the test, then getManagementName()
> returns the proper name.
> A git bisect shows
> https://github.com/apache/camel/commit/1a4e34960fb6953bb804717a728c294f27108a4f
> as the offending commit, but I can't see why it creates trouble.
> Mailing list thread:
> http://camel.465427.n5.nabble.com/Why-is-JMX-gone-after-upgrading-to-Camel-2-18-x-tt5806793.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
