Skip to content


Subversion checkout URL

You can clone with
Download ZIP


"noconnection" event not emitted if Redis goes away after the first connection #44

rjp opened this Issue · 0 comments

1 participant

rjp commented

To reproduce,
1. create a script having a redis client object and a "noconnection" listener
2. kill redis
3. run the script - noconnection event fires as expected
4. start redis
5. run the script
6. kill redis
7. script bombs out with an exception thrown and no "noconnection" event

If you remove the "throw e" under the client.maybeReconnect() call in the stream "error" listener, that behaves as expected - a stream of "reconnecting" events followed by a "noconnection" after the maximum reconnect count is reached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.