ChannelInitializer (PING before connect) waits indefinite #470
Labels
type: bug
A general bug
Milestone
Comments
mp911de
added a commit
that referenced
this issue
Feb 20, 2017
PING before activate connection now applies the configured command timeout from RedisURI to guard connection initialization. Applying the timeout monitors the PING command (AUTH for connections using a password). If the timeout is reached, the initialization future is completed with a timeout exception which closed the connection. If the PING is completed in time, command monitoring is canceled.
mp911de
added a commit
that referenced
this issue
Feb 20, 2017
PING before activate connection now applies the configured command timeout from RedisURI to guard connection initialization. Applying the timeout monitors the PING command (AUTH for connections using a password). If the timeout is reached, the initialization future is completed with a timeout exception which closed the connection. If the PING is completed in time, command monitoring is canceled.
mp911de
added a commit
that referenced
this issue
Feb 20, 2017
PING before activate connection now applies the configured command timeout from RedisURI to guard connection initialization. Applying the timeout monitors the PING command (AUTH for connections using a password). If the timeout is reached, the initialization future is completed with a timeout exception which closed the connection. If the PING is completed in time, command monitoring is canceled.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PlainChannelInitializerandSslChannelInitializerhave no timeout processing for the ping command that may run forever when the remote side is unresponsive.The text was updated successfully, but these errors were encountered: