Tests with PubSub Messaging never ends when redis crash in 3.2.1

[nicolasb29]

Tests with PubSub Messaging never ends when redis crash in 3.2.1

[mp911de]

With #2782 we reintroduced fail-safety to RedisMessageListenerContainer to continue subscription attempts. The container works the following:

1. If it cannot subscribe initially, subscription (lazyListen) fails.
2. If the initial subscription was a successful and a Redis failure occurs, the container tries to resubscribe until reaching BackOff.maxAttempts.

By default, BackOff.maxAttempts is unlimited.

[nicolasb29]

That's what I understood for the maxAttempts. So the solution is to set a maxAttempts with a FixedBackOff in my test cases when redis crash or stops too soon ? (We are using TestContainers for few years with a GenericContainer of Redis and the shutdownHook stop the Redis, so we have the loop problem. I haven't tried with the official Spring Boot support).

[mp911de]

Yes, using BackOff is the recommended approach. Spring Boot doesn't configure a container bean out of the box. However, when using Spring Session, you get a pre-configured container.

Shutdown hooks aren't reliable in terms of ordering and therefore, you experience quite some issues.

[nicolasb29]

Ok thanks ! I will use a FixedBackOff.