[
https://issues.apache.org/activemq/browse/CAMEL-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61414#action_61414
]
Ben O'Day commented on CAMEL-3009:
----------------------------------
The issue with skipping all delayed jobs, is that if a job is delayed by just a
few millis (because of high system load, etc), then it would be skipped. If we
wanted to go this route, then we'd have to set a threshold and allow the user
to specify this as well (i.e. skip any jobs delayed by more than X millis,
etc).
Instead, my approach protects against this by only preventing multiple delayed
jobs from running back-to-back. So, it will always run a delayed job no matter
how long it was delayed, but will never run the job multiple times just to
catch up, etc. If we choose this approach, perhaps there is a better name for
the parameter to make this clear ("runOnlyLastMissedJob", etc).
Either way, I'm still confused why I can't get Quart's
"trigger.misfireInstruction" parameters to work because I don't want to
reinvent the wheel. I was hoping someone from the Camel team had some insight
on this. I noticed that there weren't any unit tests for the trigger misfire
modes. I can try to add a few unit tests to prove this out a bit if we think
its worthwhile...let me know.
> 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.
