Details
-
Bug
-
Resolution: Done
-
Major
-
4.5.3.Final
-
None
-
To Reproduce
Open and run the error.zip
Call http://localhost:8080/country/sync
The 404 error is propagated to the result.
Now call http://localhost:8080/country/async
Note that the error is a generic 500. The logs mention "Handled Internally". There is no way to figure our what went wrong in the async mode.- Expected Outcome *
The async REST call should properly propagate the 404 error, just like the synchronous call does.
To Reproduce Open and run the error.zip Call http://localhost:8080/country/sync The 404 error is propagated to the result. Now call http://localhost:8080/country/async Note that the error is a generic 500. The logs mention "Handled Internally". There is no way to figure our what went wrong in the async mode. Expected Outcome * The async REST call should properly propagate the 404 error, just like the synchronous call does. - Expected Outcome *
Description
Taken from https://github.com/quarkusio/quarkus/issues/8543
Describe the bug
It seems that when using the asynchronous REST Client operators (either CompletionStage, rxJava 2.x operators, or the Mutiny operators), when the REST client encounters an error like 404, it is not able to call any exception mappers correctly, thus making it impossible to handle any HTTP errors from the rest client.
This was reported before, and either the fix applied was not working correctly, or there is a regression.
Environment (please complete the following information):
Quarkus 1.3.2.Final, OS X 10.15, Java 11 OpenJDK.
Additional context
(Add any other context about the problem here.)
Previously reported in #3655 - the issue seems to be closed after a fix was applied, but the issue persists.
