camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CAMEL-8076) We should avoid check the
Date Sun, 23 Nov 2014 03:42:12 GMT
Willem Jiang created CAMEL-8076:
-----------------------------------

             Summary: We should avoid check the
                 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


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}
ava.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)

Mime
View raw message