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

IOException Issues Randomly #131

Open
jeepMan79 opened this issue May 31, 2018 · 1 comment
Open

IOException Issues Randomly #131

jeepMan79 opened this issue May 31, 2018 · 1 comment

Comments

@jeepMan79
Copy link

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!!

@vtortola
Copy link
Owner

vtortola commented Jun 1, 2018

Hi,

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.

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

2 participants