what it does do it calls methods such as onWebsocketCloseInitiated or onWebsocketClosing on the current thread. what it doesn't do it doesn't call onClose, does not close the socket and doesn't interrupt the thread. closeBlocking hangs forever.
i found that getConnection().closeConnection(1000, "foo") does close the connection with the respective code and message and is safe to call after close().
i'm not sure whether it is how i'm supposed to close the WebSocketClient, but a method called close that doesn't close anything looks highly suspicious, and i didn't manage to find any meaningful documentation, so i'm creating this issue.
tested on 1.3.0 (from maven) and 58d1778
what it does do it calls methods such as
onWebsocketCloseInitiatedoronWebsocketClosingon the current thread. what it doesn't do it doesn't callonClose, does not close the socket and doesn't interrupt the thread.closeBlockinghangs forever.i found that
getConnection().closeConnection(1000, "foo")does close the connection with the respective code and message and is safe to call afterclose().i'm not sure whether it is how i'm supposed to close the WebSocketClient, but a method called
closethat doesn't close anything looks highly suspicious, and i didn't manage to find any meaningful documentation, so i'm creating this issue.tested on 1.3.0 (from maven) and 58d1778