Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduler - support non-blocking scheduled methods #24621

Closed
mkouba opened this issue Mar 30, 2022 · 2 comments · Fixed by #24658
Closed

Scheduler - support non-blocking scheduled methods #24621

mkouba opened this issue Mar 30, 2022 · 2 comments · Fixed by #24658
Labels
Milestone

Comments

@mkouba
Copy link
Contributor

mkouba commented Mar 30, 2022

Description

Currently, a scheduled method is always invoked on a thread from the core thread pool. As a result, you can't e.g. use Hibernate Reactive in a scheduled method. A workaround is to inject the managed Vertx and use Vertx.runOnContext().

We could either use @io.smallrye.common.annotation.NonBlocking to mark a scheduled method as non-blocking or allow a scheduled method to return an async type such as Uni.

Implementation ideas

No response

@mkouba mkouba added the kind/enhancement New feature or request label Mar 30, 2022
@mschorsch
Copy link
Contributor

See also #21428

@mkouba
Copy link
Contributor Author

mkouba commented Mar 30, 2022

See also #21428

Yup, that would be the next phase ;-).

mkouba added a commit to mkouba/quarkus that referenced this issue Mar 31, 2022
mkouba added a commit to mkouba/quarkus that referenced this issue Mar 31, 2022
mkouba added a commit to mkouba/quarkus that referenced this issue Mar 31, 2022
mkouba added a commit to mkouba/quarkus that referenced this issue Mar 31, 2022
mkouba added a commit to mkouba/quarkus that referenced this issue Apr 1, 2022
@quarkus-bot quarkus-bot bot added this to the 2.9 - main milestone Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants