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
Randomly, we will get IOExceptions in both AwaitHeaderAsync and WriteInternal methods.
2018-04-14 11:58:08,027 [187] ERROR vtortola.WebSockets.Rfc6455.WebSocketConnectionRfc6455 [] - IOException in AwaitHeaderAsync:Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2018-04-14 11:58:08,027 [187] ERROR vtortola.WebSockets.Rfc6455.WebSocketConnectionRfc6455 [] - IOException in WriteInternal-Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
Also, in the packet captures, the client tries to make a connection and the websocket server responds with a RST, ACK.
The only way to clear this up is with a service restart. Any ideas?
Thanks!!
The text was updated successfully, but these errors were encountered:
Did you configure ping timeout? are you reading from the connection even if you are not expecting anything?
Those errors look like normal disconnections due the socket dying, but the fact you have to restart the service is very strange. Could you provide more details about how do you configure the component, version and operating system? Thanks.
Hi,
Randomly, we will get IOExceptions in both AwaitHeaderAsync and WriteInternal methods.
2018-04-14 11:58:08,027 [187] ERROR vtortola.WebSockets.Rfc6455.WebSocketConnectionRfc6455 [] - IOException in AwaitHeaderAsync:Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2018-04-14 11:58:08,027 [187] ERROR vtortola.WebSockets.Rfc6455.WebSocketConnectionRfc6455 [] - IOException in WriteInternal-Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
Also, in the packet captures, the client tries to make a connection and the websocket server responds with a RST, ACK.
The only way to clear this up is with a service restart. Any ideas?
Thanks!!
The text was updated successfully, but these errors were encountered: