Pub-Sub Race conditions on high load - Subscription has been unsubscribed and cannot be used anymore

[IZWO]

After having a high load, the redis connections get closed automatically and error "Subscription has been unsubscribed and cannot be used anymore" is thrown.
We use the pub/sub event.
Bypass: if we uncomment the line

redisMessageListenerContainer.addMessageListener(listenerAdapter, new PatternTopic("Dummy"));

then it keeps working.
We have 3 Redis Machines in a cluster. See the attached example code and some logging in the target folder.

[IZWO]

Bugfix.zip

[captrespect]

any way to mitigate this issue or work around it? I'm not sure how to recover from it other than restarting our spring server.

[IZWO]

any way to mitigate this issue or work around it? I'm not sure how to recover from it other than restarting our spring server.
Yes, with uncommenting the dummy as stated above

[caiuswang]

This maybe a concurrency scenario bug that you can use by adding a persistent subscription (not unsbscribe). For example, when the application starts, a nothing_channel subscription is added. You can see if this works to you.