End Vert.x response before propagating mapped exception in VertxBlockingoutput #21841
Labels
area/resteasy-classic
area/vertx
kind/bug
Something isn't working
triage/out-of-date
This issue/PR is no longer valid or relevant
Comments
|
Should this be closed now that #21842 is in? |
|
Possible reproducer: #21762 (comment) |
|
@geoand Closing, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When an exception is thrown when processing the write stream, Resteasy does not close the Vert.X response prior to propagating the exception.
This behavior might cause applications to not receive events from Vert.X (e.g.: when using a filter that adds a headers handler) because the response is not ended properly.
Similarly to when there is no data to write, the
VertxBlockingoutputshould make sure the response is ended.Related to this issue #21762.
Expected behavior
Properly end the Vert.x response.
Actual behavior
Vert.x response not properly ended when an exception occurs on the write stream.
How to Reproduce?
See #21762.
Output of
uname -aorverLinux fedora 5.14.18-200.fc34.x86_64 #1 SMP Fri Nov 12 16:48:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.4+
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
Resteasy classic issue.
The text was updated successfully, but these errors were encountered: