[
https://issues.apache.org/activemq/browse/CAMEL-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61488#action_61488
]
Hadrian Zbarcea commented on CAMEL-3009:
----------------------------------------
I wonder if this option is really needed. I think camel can infer the needed
info.
Storing the timestamp of the last start or resume allows camel to know if the
last job should have been executed and should not skip missed jobs because of
milliseconds (or longer delays). If it doesn't behave like this it should be
fixed. This should sort out your issue with skipping all missed job.
The second issue that refers to how many past jobs to rerun, imho is a non
issue, because the value of your cron trigger is application dependent and you
have the option of keeping camel active or paused. (I'll take a look at
trigger.misfireInstruction too).
Personally I prefer to keep the camel interface as simple as possible.
> Add option to quartz consumer to ignore jobs being triggered due restarting
> ---------------------------------------------------------------------------
>
> Key: CAMEL-3009
> URL: https://issues.apache.org/activemq/browse/CAMEL-3009
> 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.
