camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben O'Day (JIRA)" <>
Subject [jira] Commented: (CAMEL-3009) Add option to quartz consumer to ignore jobs being triggered due restarting
Date Sun, 29 Aug 2010 20:43:41 GMT


Ben O'Day commented on CAMEL-3009:


I found out why I couldn't get the trigger.misfireInstruction modes to work.  There is a property
called "org.quartz.jobStore.misfireThreshold" which defaults to 60s.  This is used to determine
is a job is marked as "misfired" default, this happens only if the job is 60s behind.
 My unit tests were never reaching this threshold, so the misfire logic never kicked-in and
all jobs just ran immediately when resumed.  I changed this threshold to 1s and my test now
behaves appropriately (no catchup jobs, etc).

So, I think the misfire handling works as desired for all jobs that are more than 60s late
(or less if configured explicitly) patch required.

> Add option to quartz consumer to ignore jobs being triggered due restarting
> ---------------------------------------------------------------------------
>                 Key: CAMEL-3009
>                 URL:
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-quartz
>    Affects Versions: 2.4.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.5.0
>         Attachments: camel-quartz-maxTimeDelay-patch.txt, camel-quartz-skip-missed-jobs-patch.txt
> Quartz scheduler may by default try to catch up if a quartz consumer has been stopped
for a while.
> Then when its started it may trigger a series of jobs due they were supposed to be triggered
if the consumer has been always running.
> We should make it easy to configure an option to tell Camel to ignore those jobs.
> For example if you have a trigger to run every 5th second. And you pause a consumer for
2 hours. You may not want quartz to fire 12 * 60 * 2 jobs when its started to catch up for
those 2 hours.
> Quartz itself may have an option you can configure on the job but it may not be obviously
how to do this.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message