Fix channel loss on reconnect

[kichik]

The scenario requires two or more close-by disconnections

1. Connect to Redis
2. Subscribe successfully to a channel
3. Forcibly kill the connection (by taking down Redis for example)
4. Let lettuce reconnect successfully
5. Forcibly kill the connection again right before activate() successfully subscribes
6. Let lettuce reconnect successfully
7. RedisPubSubConnectionImpl.channels is empty and the channel will stay unsubscribed

There doesn't seem to be a reason to clear out channels and patterns.
It is only used for persistence over different connections.
There is no downside to having a channel in that set even if the subscription was not successful.

[coveralls]

Coverage increased (+0.08%) to 96.29% when pulling f6b869a on kichik:master into cc638d4 on mp911de:master.

[mp911de]

Looks good to me. Both collections patterns and channels are sets. A redis reply of subscribed to the pattern/channel won't cause duplicates. Thank you for the PR.

[kichik]

Thanks for the super fast response (again)!
Any chance you can release 3.0.3 with this?

[mp911de]

Will do. Could you check the memory leak fix I pushed earlier this day?

Von meinem iPhone gesendet

Am 31.01.2015 um 20:02 schrieb kichik notifications@github.com:

Thanks for the super fast response (again)!
Any chance you can release 3.0.3 with this?

—
Reply to this email directly or view it on GitHub.