[
https://issues.apache.org/activemq/browse/CAMEL-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61451#action_61451
]
Claus Ibsen commented on CAMEL-3009:
------------------------------------
The problem with keep the last misfired is that what if you have a cron which
should trigger at noon every wednesday.
Then you suspend the Camel app (with this quartz job) on monday, and resume it
on friday. Then you may not want the misfired job to trigger asap, but instead
wait for next wednesday to fire.
So at least there should be an option to select the strategy. For example we
could introduce an enum with the choices such as:
{{onResumeRunMissedJobs}}
- none
- onlyLast
- all
> 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-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.
