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
Timeout in WebSocketClient not used #177
Comments
yeah its true that the timeout is currently not used. 2013/5/3 sfroeth notifications@github.com
|
…TallNate#88, TooTallNate#155, TooTallNate#167, TooTallNate#175, TooTallNate#177, TooTallNate#187) (changes not yet fully tested)
…TallNate#88, TooTallNate#155, TooTallNate#167, TooTallNate#175, TooTallNate#177, TooTallNate#187) (changes not yet fully tested)
Hi,
One of the constructors of WebSocketClient takes a value for a timeout, but it is actually never used. The default timeout used by SocketChannel.connect() seems to be something around two minutes if the remote host does not answer. For my use case much shorter timeouts are necessary. I fixed it for me using a thread and calling SocketChannel.close():
// method interruptibleRun():
Regards
Stefan
The text was updated successfully, but these errors were encountered: