-
Notifications
You must be signed in to change notification settings - Fork 927
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
Some annotated service methods are run from blocking task executors. #2078
Labels
Comments
I will work on it! |
minwoox
pushed a commit
that referenced
this issue
Oct 24, 2019
Motivation: The annotated services whose return type is neither `HttpResponse` nor `CompeltableFuture`, are run using a `blockingTaskExecutor` by default. We should fix this to use `EventLoop` by default and let a user choose to use `blockingTaskExecutor` if he/she wants. Modifications: - Add `@Blocking` which makes the annotated service run using `blockingTaskExecutor` - Make all annotated services run from `EventLoop` Result: - Fix #2078 - (Breaking) All annotated services are now run from `EventLoop` by default
eugene70
pushed a commit
to eugene70/armeria
that referenced
this issue
Nov 10, 2019
…e#2187) Motivation: The annotated services whose return type is neither `HttpResponse` nor `CompeltableFuture`, are run using a `blockingTaskExecutor` by default. We should fix this to use `EventLoop` by default and let a user choose to use `blockingTaskExecutor` if he/she wants. Modifications: - Add `@Blocking` which makes the annotated service run using `blockingTaskExecutor` - Make all annotated services run from `EventLoop` Result: - Fix line#2078 - (Breaking) All annotated services are now run from `EventLoop` by default
fmguerreiro
pushed a commit
to fmguerreiro/armeria
that referenced
this issue
Sep 19, 2020
…e#2187) Motivation: The annotated services whose return type is neither `HttpResponse` nor `CompeltableFuture`, are run using a `blockingTaskExecutor` by default. We should fix this to use `EventLoop` by default and let a user choose to use `blockingTaskExecutor` if he/she wants. Modifications: - Add `@Blocking` which makes the annotated service run using `blockingTaskExecutor` - Make all annotated services run from `EventLoop` Result: - Fix line#2078 - (Breaking) All annotated services are now run from `EventLoop` by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related: #2064
For example, when the return type of a service method is
AggregatedHttpResponse
or response object conversion is involved, the service method is currently executed via the blocking task executor. By contrast, if a service method returnsHttpResponse
, it will be executed from a event loop thread. This behavioral difference is too subtle and confusing.We need to:
The text was updated successfully, but these errors were encountered: