Reactive rest client custom exception mapper is invoked twice #19476
Comments
|
The problem is in the fact that client response filters are invoked in the abort chain. I think we need to have a different abort chain, without them, if the filters execution has started. I'll try to create a PR for it |
michalszynkiewicz
added a commit
to michalszynkiewicz/quarkus
that referenced
this issue
Aug 19, 2021
michalszynkiewicz
added a commit
to michalszynkiewicz/quarkus
that referenced
this issue
Aug 20, 2021
michalszynkiewicz
added a commit
to michalszynkiewicz/quarkus
that referenced
this issue
Aug 20, 2021
michalszynkiewicz
added a commit
to michalszynkiewicz/quarkus
that referenced
this issue
Aug 23, 2021
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Aug 24, 2021
…ey fail fixes quarkusio#19476 (cherry picked from commit 873c895)
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Aug 25, 2021
…ey fail fixes quarkusio#19476 (cherry picked from commit 873c895)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I register my custom exception mapper to a client wit
@RegisterProviderthen the both methods ofResponseExceptionMapper<T>are invoked twice.Expected behavior
The invocation is done just once.
Actual behavior
No response
How to Reproduce?
Reproducer: https://github.com/mkonzal/quarkus-reactive-response-exception-mapper.git
Step to reproduce GET /service/connect
Output of
uname -aorverNo response
Output of
java -versionopenjdk version "11.0.12" 2021-07-20 LTS
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.1.2
Build tool (ie. output of
mvnw --versionorgradlew --version)Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Additional information
No response
The text was updated successfully, but these errors were encountered: