-
Notifications
You must be signed in to change notification settings - Fork 352
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
NPE in websocket server if client has keepAlive #462
Comments
The release in the finally block is called before anyone has a chance to subscribe to the returned mono. So even on synchronous scheduler it won't work if the ref count of frame's content was 1. With tcp it's 2 but I don't know exactly why. |
Closing as I'm using this in rsocket-cli |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I create my websocket client with keepAlive like this
the server throws npe (see below) when it receives the keep alive frame.
The strange thing is that I do not see this with tcp transport at least for ping pong tests.
I'm just guessing that the problem is somewhere in
WebsocketDuplexConnection
or probably inFragmentationDuplexConnection
if the websocket frames are not sized same as tcp?The text was updated successfully, but these errors were encountered: