You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: