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

[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);
  camelContext.setAllowUseOriginalMessage(false);
  camelContext.setNameStrategy(new
ExplicitCamelContextNameStrategy(CAMEL_CONTEXT_NAME));

camelContext.getShutdownStrategy().setTimeout(Long.parseLong(System.getProperty(SHUTDOWN_TIMEOUT,
"10")));
}

And then I refer to the context:

@Configuration
public class HealthConfig implements InitializingBean {

  @Autowired private CamelContext camelContext;

  @Override
  public void afterPropertiesSet() throws MalformedObjectNameException {
    String mgmtName = camelContext.getManagementName();
  }
}

With 2.17.7, mgmtName is set.  With 2.18.0 (and above), mgmtName is null.

I upgraded simply by replacing "2.17.7" with "2.18.0" (i have tried later
versions as well) in the Gradle configuration.

Best regards,
Henrik