Resubscript redis listener on subscript task run occured exception [DATAREDIS-231]

[spring-projects-issues]

jokeway opened DATAREDIS-231 and commented

When Subscript task occured exception( Network problem/Redis server start etc.), the subscript task will abort run method and the whole listener thread will exist.

In the production environment, it is better to reconnection and resubscript

---

Affects: 1.1.0.M1

Reference URL: #11

[spring-projects-issues]

Jennifer Hickey commented

I do agree we should have this functionality. I'll comment on the PR individually, but do want to note that the fix will only work when using Jedis. SRP and Lettuce don't block on the subscribe call, so that Thread wouldn't even be running when the Redis server went down. Lettuce reconnects Subscriptions automatically, so this already works. I need to research the best way to handle this with SRP, as currently there is no indication that the subscription was lost on Redis restart

[spring-projects-issues]

Jennifer Hickey commented

Opened this issue for SRP: spullara/redis-protocol#32

We will go ahead and implement the Jedis case in this release