-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Vertx Thread blocked even with @Blocking on gRPC service #45830
Labels
Comments
/cc @alesj (grpc), @cescoffier (grpc) |
Additional stack traces:
This stack trace on the other hand might be an indication that the underlying system might really be at the edge:
|
It's still making progress. In such a case, I would extend the Vert.x Thread checker timer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The Vertx thread is blocked, even though the @Blocking annotation is used to indicate work should be done on a dedicated worker thread.
Expected behavior
With the @Blocking annotation, my expectation would be that all work is done in worker threads.
The parsing of the gRPC message can be CPU intensive, especially for larger messages. If the system is under heavy load, then the Vertx thread should not be blocked.
Actual behavior
How to Reproduce?
I can try to create a reproducer, if this is accepted as bug.
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
3.14.4
Build tool (ie. output of
mvnw --version
orgradlew --version
)Gradle 8.9
Additional information
application.properties
:The text was updated successfully, but these errors were encountered: