[CAMEL-18318] camel-quartz - Context fails to start when one of the cron configuration has expired

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.14.5, 3.18.1, 3.19.0
• Component/s: camel-quartz
• Estimated Complexity: Unknown
• Flags: Important
• Assignee: Claus Ibsen
• Reporter: Prasanth Ganesh Rao
• Created: 28/Jul/22 06:15
• Updated: 01/Aug/22 10:17
• Resolved: 28/Jul/22 14:43

Description

We have integration scenarios with muliple quartz from endpoints in a single camel context deployed as osgi bundles. We observe that if one of the quartz configuration has no more schedules and if the bundle were to get restarted, the entire context fails to start thereby preventing future execution of other routes. Error seen in the stacktrace

Caused by: org.apache.camel.RuntimeCamelException: org.quartz.SchedulerException: Based on configured schedule, the given trigger 'myGroup.expired' will never fire.
    at org.apache.camel.RuntimeCamelException.wrapRuntimeException(RuntimeCamelException.java:66)

The issue is becoming a blocker for our scenarios with multiple custom future schedules. Updating the quartz configuration each time we encounter the error is becoming difficult. Hence requesting your quick insights and a resoultion.

I am enclosing a junit to help you recreate the issue. quartz-error.zip The scenario has two routes expiredScheduleRoute and recurringScheduleRoute. The expectation is that the context starts and recurringScheduleRoute continues to run every 2 seconds. I believe we may need a parameter to the quartz endpoint to skip the validation for expiredScheduleRoute

 

 

Issue Links

• is fixed by: CAMEL-18319 camel-core - Supervising route controller should not eager warmup routes