[
https://issues.apache.org/jira/browse/CAMEL-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434516#comment-15434516
]
ASF GitHub Bot commented on CAMEL-7132:
---------------------------------------
GitHub user YoshikiHigo opened a pull request:
https://github.com/apache/camel/pull/1137
Followup to CAMEL-7132
This commit is a small followup to CAMEL-7132
(ca124fd2906071db794e6f539379be637144110a).
Yoshiki, Shinpei, Hideaki, and Mei
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/YoshikiHigo/camel fix05
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1137.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1137
----
commit 098468ebda766dda500bd0f525787db80da7c083
Author: Yoshiki Higo <[email protected]>
Date: 2016-08-24T08:45:45Z
Followup to CAMEL-7132
----
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.12.3, 2.13.0
>
>
> 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.3.4#6332)
