Skip to content
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 connection is lost without notifying client #1773

Open
rgupt102 opened this issue Feb 12, 2021 · 0 comments
Open

Websocket connection is lost without notifying client #1773

rgupt102 opened this issue Feb 12, 2021 · 0 comments

Comments

@rgupt102
Copy link

I am using async http websocket client to send requests and I have observed many times that connection is lost without calling onClose callback. websocket stays open (websokcet.isOpen still true)but no requests are sent to server. A connection interrupt doesn't close the Netty websocket and doesn't trigger the disconnected event.
It is difficult to catch the disconnection , so i am not able to retry for the connection. I have retrial logic in onClose callback but for this issue onClose is not event called.
I see there is no support for onConnectionLost as we have in - TooTallNate/Java-WebSocket#473
implementing custom heartbeats through ping/pong would be tricky. please help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant