-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
WebSocket Next Server-Side Streaming cancelation #41025
Comments
andlinger
changed the title
WebSocket Next Server-Side Streaming canceling
WebSocket Next Server-Side Streaming cancelation
Jun 6, 2024
cc @mkouba |
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
Jun 7, 2024
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
Jun 7, 2024
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jun 11, 2024
- fixes quarkusio#41025 (cherry picked from commit 787c9d6)
holly-cummins
pushed a commit
to holly-cummins/quarkus
that referenced
this issue
Jul 31, 2024
danielsoro
pushed a commit
to danielsoro/quarkus
that referenced
this issue
Sep 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If a server-side streaming connection is closed by the client, the subscription of Multi should also be cancelled.
Expected behavior
The returned
Multi<Product>
should be cancelled if the client closes the WebSocket connection.Actual behavior
The
Mutli<Product>
subscription stays active and produces following exceptions every tick:How to Reproduce?
Created a reproducer: https://github.com/andlinger/quarkus-reproducer/tree/quarkus-41025
The text was updated successfully, but these errors were encountered: