-
Notifications
You must be signed in to change notification settings - Fork 275
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
Re-open a closed websocket, get an exception of "An unhandled exception of type #99
Comments
Could you try the latest version: 0.15? |
Kerry,
Sorry that I missed your previous communication. I will pick up the latest
version.
Thanks
Jimmy
…On Mon, Sep 4, 2017 at 11:37 PM, Kerry Jiang ***@***.***> wrote:
Could you try the latest version: 0.15?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#99 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Aac_y8j-gVq2OPZ0VWVy8dUqUKSoEhXuks5sfNAmgaJpZM4OahhW>
.
|
Same issue here. What can be the cause? @kerryjiang |
Same issue for me too also with the latest version. Any news here? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
'System.Exception' occurred in SuperSocket.ClientEngine.dll
Additional information: The socket is connected, you needn't connect again! occurred
Hi Kerry,
In an error handling case, our design of the handler of websocket Closed event will try to re-establish the connection. The connection code looks like :
if(!(websocket.state == WebSocketState.Open))
{
websocket.open();
}
In one of the test case, we shut down the websocket server at the server side, it is found that the code does not work all the time, the above exception was thrown in some instances.
When the exception was thrown, we noticed that the websocket.state was closed, as expected.
Any reason why the socket is still connected, when the websocket is closed?
Thanks
Jimmy
The text was updated successfully, but these errors were encountered: