[CAMEL-8076] We should avoid checking the DupTriggerKey if the recoverableJob is true

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.13.4, 2.14.1, 2.15.0
• Component/s: camel-quartz2
• Estimated Complexity: Unknown
• Assignee: Willem Jiang
• Reporter: Willem Jiang
• Created: 23/Nov/14 03:41
• Updated: 28/Jun/16 07:18
• Resolved: 24/Nov/14 03:11

Description

Here is a stackoverflow question which shows when the clustered quartz wants to recovery the job, camel throw the java.lang.IllegalArgumentException:

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)

We should avoid the checking of ensureNoDupTriggerKey, if the recoverableJob is true.