CalendarIntervalSchedule is firing non-stop for 10 mins on the day that DST begins (and we lose an hour). #2309
Replies: 1 comment
-
I moved this to a bug report: #2349 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Consider a Calendar Interval Schedule that:
So far all seems correct. However, when 3/10/2024 3:00 AM comes around - the trigger fires non-stop for 10 mins exactly. It is almost like the next fire time never calculates a good time after 3/10/2024 3:00 AM. We had one trigger fire > 30k times.
I can repro this in the
TriggerUtils.ComputeFireTimes
method as well. I've attached an annotated sample whereTriggerUtils.ComputeFireTimes
is doing exactly what I am seeing when Quartz do - it gets stuck on 3/10/2024 3:00 AM.QuartzDstRepro.zip
If you open that SLN and run it, you will see where it fails and the annotations will describe the problem.
Thanks in advance for any help!
Beta Was this translation helpful? Give feedback.
All reactions