[jira] [Resolved] (CAMEL-8076) We should avoid checking the DupTriggerKey if the recoverableJob is true

["Willem Jiang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang resolved CAMEL-8076.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.13.4
                   2.15.0
                   2.14.1

Applied the patch into camel master, camel-2.14.x and camel-2.13.x branches.

> We should avoid checking the DupTriggerKey if the recoverableJob is true
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-8076
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8076
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-quartz2
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.14.1, 2.15.0, 2.13.4
>
>
> Here is [a stackoverflow question|http://stackoverflow.com/questions/27031971/quartz-clustering-in-camel-spring-dsl] which shows when the clustered quartz wants to recovery the job, camel throw the java.lang.IllegalArgumentException:
> {code}
> Java.lang.IllegalArgumentException: Trigger key cluster.quartz is already in used by Endpoint[quartz2://cluster/quartz?cron=0+0%2F2+++*+%3F&durableJob=true&recoverableJob=true&stateful=true] at org.apache.camel.component.quartz2.QuartzEndpoint.ensureNoDupTriggerKey(QuartzEndpoint.java:272)
> {code} 
> We should avoid the checking of ensureNoDupTriggerKey, if the recoverableJob is true.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)