[CAMEL-19914] Start and stop a quartz route messes up its schedule

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 3.20.6
• Component/s: camel-quartz
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: John Yin
• Created: 26/Sep/23 00:00
• Updated: 14/Oct/23 23:28
• Resolved: 26/Sep/23 04:34

Description

When a stopped quartz route is resumed, if it has missed a previously scheduled firing because of the stop, it would immediately fire regardless its defined schedule.  Here is an example:

from("quartz://test?cron=0+0/3+?+*").routeId("ROUTE_test").autoStartup(true).log("in test")

 

from("timer://start_stop_test?repeatCount=1").autoStartup(true)

    .process(

{         // stop route "ROUTE_test" using routeController API         // wait for more than 3 minutes so that the stopped ROUTE_test will miss a firing         // resume route "ROUTE_test" using routeController API.  You will see ROUTE_test immediately fire regardless whether it is the scheduled time or not.     }

)

Issue Links

• relates to: CAMEL-19988 camel-core - PropertyBindingSupport - Should not hide IllegalArgumentException with real cause if failing to set property