You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/08/01 10:18:00 UTC
[jira] [Updated] (CAMEL-18318) camel-quartz - Context fails to start when one of the cron configuration has expired
[ https://issues.apache.org/jira/browse/CAMEL-18318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-18318:
--------------------------------
Fix Version/s: 3.14.5
> camel-quartz - Context fails to start when one of the cron configuration has expired
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-18318
> URL: https://issues.apache.org/jira/browse/CAMEL-18318
> Project: Camel
> Issue Type: Improvement
> Components: camel-quartz
> Reporter: Prasanth Ganesh Rao
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.14.5, 3.18.1, 3.19.0
>
> Attachments: quartz-error.zip
>
>
> 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_
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)