Provide a new ApplicationNotRunning predicate for @Scheduled
#24605
Conversation
extensions/scheduler/runtime/src/main/java/io/quarkus/scheduler/Scheduled.java
Outdated
Show resolved
Hide resolved
...r/deployment/src/test/java/io/quarkus/scheduler/test/ApplicationNotRunningPredicateTest.java
Outdated
Show resolved
Hide resolved
The `@Scheduled` annotation's `skipExecutionIf` attribute can be used to skip individual executions in a schedule. Currently, Quarkus only provides the `Never` implementation, which is also the default (never skips an execution). Since the scheduler is initialized very early (priority `PLATFORM_BEFORE`) it can happen that executions get scheduled before the application has been fully started. An application can solve this by itself waiting to get notified with the `StartupEvent` or it can now use this new predicate: `@Scheduled(..., skipExecutionIf = ApplicationNotRunning.class)`.
knutwannheden
force-pushed
the
applicationnotrunning-skippredicate
branch
from
8c694ed to
785e88a
Compare
|
As a user I wonder if this should become the default at some point (I was unaware the scheduler could start tasks before the application is started, and I wonder how useful that is or why I might want that) |
Well, it depends on how you define "application is started". The only "hard requirement" for scheduled methods is that the CDI container must be running. And in many cases, it's OK to execute a scheduled method |
The
@Scheduledannotation'sskipExecutionIfattribute can be used to skip individual executions in a schedule. Currently, Quarkus only provides theNeverimplementation, which is also the default (never skips an execution).Since the scheduler is initialized very early (priority
PLATFORM_BEFORE) it can happen that executions get scheduled before the application has been fully started. An application can solve this by itself waiting to get notified with theStartupEventor it can now use this new predicate:@Scheduled(..., skipExecutionIf = ApplicationNotRunning.class).