[
https://issues.apache.org/jira/browse/CAMEL-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991517#comment-12991517
]
Bryan Keller commented on CAMEL-3606:
-------------------------------------
I ran my test using the latest 2.7 snapshot and the problem seems to be fixed.
> Regression in stateful job support caused by duplicate job name check added
> in camel-quartz 2.6
> -----------------------------------------------------------------------------------------------
>
> Key: CAMEL-3606
> URL: https://issues.apache.org/jira/browse/CAMEL-3606
> Project: Camel
> Issue Type: Bug
> Components: camel-quartz
> Affects Versions: 2.6.0
> Environment: Java 1.6.0_22
> Reporter: Bryan Keller
> Assignee: Tracy Snell
> Fix For: 2.7.0
>
>
> A change in Camel 2.6 causes an exception to be thrown when using a stateful
> Quartz job in a non-clustered environment. Upon first startup, the job is
> persisted in the job store (e.g. database). If the app is restarted, it
> appears Camel is trying to recreate the persisted job and fails, thinking it
> is creating a duplicate schedule.
> e.g. Using an endpoint such as:
> {code}
> <endpoint id="pingSchedule"
> uri="quartz://myapp/ping?cron=${ping.cron}&stateful=true" />
> {code}
> Configure the Quartz job store to NOT be clustered
> (org.quartz.jobStore.isClustered = false). Start the app. Then shut it down.
> Now start it up a second time. The following exception is thrown:
> {code}
> org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint:
> quartz://myapp/ping?cron=0+0+23+*+*+%3F&stateful=true due to: A Quartz job
> already exists with the name/group: myapp/ping
> {code}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
