Nathan Jensen created CAMEL-7132:
------------------------------------
Summary: QuartzComponent with custom Scheduler and multiple
contexts requires JMX to be enabled
Key: CAMEL-7132
URL: https://issues.apache.org/jira/browse/CAMEL-7132
Project: Camel
Issue Type: Bug
Components: camel-quartz
Affects Versions: 2.11.2
Reporter: Nathan Jensen
Priority: Minor
If you have a custom Scheduler set on the QuartzComponent and multiple camel
contexts per scheduler, then you must have JMX enabled for it work right.
Ideally, it should not require JMX to be enabled to work correctly.
Specifically, QuartzComponent.onCamelContextStarted(CamelContext, boolean) will
make a map key that depends on the context's managementName, which is not set
if JMX is not enabled. Without a managementName, all contexts with quartz
routes end up with a key named CamelQuartzCamelContext - null, and then when
the CamelJob executes it will retrieve the wrong context.
Note we worked around this by injecting a custom LifecycleStrategy that sets
the managementName in onContextStart(). But ideally we shouldn't have to do
that.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
