quarkus-scheduler: Timestamps of the current run and the previous run are indistinguishable #40789
Unanswered
JBartscher
asked this question in
Q&A
Replies: 2 comments 1 reply
-
I found a very similar Quarkus issue that might be of interest to you - #37567 @mkouba's answer there says:
I also tried looking into Quartz's API which have very similar methods (see here) but nonexistent javadoc to explain what the diff should be :-/ |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I have noticed a peculiarity in the extension quarkus-scheduler that I am not sure if it is a bug or if I am simply using the lib incorrectly.
The issue is that the quarkus-scheduler uses the ScheduledExecution class to map the context of a task scheduled by the scheduler. This allows the execution time to be determined using the
getScheduledFireTime()
function. The trigger can also be accessed usinggetTrigger()
. This in turn offers the functiongetPreviousFireTime()
to terminate the last run of the task.Now the curious thing: these two timestamps are identical.
Am I using the scheduler and its methods incorrectly or is this an actual bug?
Ive set up a minimal example to test this behavior if anyone want to have a look at it.
https://github.com/JBartscher/scheduler-ctx-timestamp-bug
Ive tested it with Quarkus in Version 3.10.1
Beta Was this translation helpful? Give feedback.
All reactions