Mutiny Dropped Exception on SSE Cancel #27489
Comments
|
/cc @cescoffier, @jponge |
|
When do these show up? |
Does the reproducer not work for you? |
|
I missed that, sorry |
cescoffier
added a commit
to cescoffier/quarkus
that referenced
this issue
Aug 29, 2022
cescoffier
added a commit
to cescoffier/quarkus
that referenced
this issue
Aug 29, 2022
fercomunello
pushed a commit
to fercomunello/quarkus
that referenced
this issue
Aug 31, 2022
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 5, 2022
Fix quarkusio#27489. (cherry picked from commit d876224)
evanchooly
pushed a commit
to nenros/quarkus
that referenced
this issue
Sep 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Undesirable
ERRORmessage appears in logs, e.g:2022-08-25 11:30:51,013 ERROR [io.qua.mut.run.MutinyInfrastructure] (vert.x-eventloop-thread-2) Mutiny had to drop the following exception: io.vertx.core.http.HttpClosedException: Connection was closedExpected behavior
Would prefer not to have these appearing in Production logs. Can they be avoided or suppressed?
Actual behavior
No response
How to Reproduce?
https://github.com/jimbogithub/mutiny-sse
Run the server and the client. Observe client logs.
Output of
uname -aorverNo response
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
Mutiny SSE otherwise looks much better than legacy SSE (#23997).
The text was updated successfully, but these errors were encountered: