[CAMEL-17446] Trigger start time for Quartz causes confusion with short trigger intervals

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.13.0
• Fix Version/s: 3.15.0
• Component/s: camel-quartz
• Estimated Complexity: Unknown
• Assignee: Karen Lease
• Reporter: Karen Lease
• Created: 06/Jan/22 16:21
• Updated: 21/Jan/22 16:52
• Resolved: 21/Jan/22 16:52

Description

An issue reported on the users list shows that using trigger.repeatInterval=1200 causes the first 2 events to be fired sooner than expected after the scheduler is started.

This is due to the delay between creating the Quartz Trigger and when the scheduler is started.

Changing the log message to show the milliseconds in the trigger's next fire time would be helpful. In addition, it appears counter-intuitive that triggerStartDelay is ignored if positive, as shown in QuartzEndpoint.createTrigger() below:

if (getComponent().getScheduler().isStarted() || triggerStartDelay < 0) {
    triggerBuilder.startAt(new Date(System.currentTimeMillis() + triggerStartDelay));
}

Is this intentional?

Issue Links

• relates to: CAMEL-17133 camel-quartz: allow missfire execution for cron triggers
• links to: GitHub Pull Request #6711