-
Notifications
You must be signed in to change notification settings - Fork 37
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
JobCancellationException after client closes connection #211
Comments
Hey, if I understand correctly, you get an error on server side, right? And from stacktrace I see, that the error thrown from |
Thanks for looking into this! Yes, the error is on server side. If the websocket is not closed then |
The main question is, what happens on ktor side, when closing HttpClient. Will it even try to close open websocket session safely (via |
That would be great, are you still planning to look into it @olme04? |
Yes, I will look into it in coming days |
will be fixed on ktor side here: https://youtrack.jetbrains.com/issue/KTOR-5016/Channel-was-closed-exception-in-WebSocket-during-normal-use |
When using ktor with a
requestStream
handler like thisI get the following exception after the client closes the connection:
I'm executing the following code on the client side:
The full example project to reproduce the error: https://github.com/Alexander-N/ktor-rsocket-error
The text was updated successfully, but these errors were encountered: