[Spring Session Redis] Web session expiration notifications not delayed until application is up again?

[fbeaufume]

I opened a question on Stack Overflow but got no anwser yet, see https://stackoverflow.com/questions/69346392/spring-session-redis-web-session-expiration-notifications-not-delayed-until-appl

Current Behavior

Currently using Spring Session Redis in a Spring Boot 2.5.3 web application.

The application correctly receives web session expiration notifications from Redis, but AFAIK only if the application is up and running at that time. It seems that if the backend is stopped at that time (crash, planned maintenance, ...), the notifications are not "kept" or "delayed" until the backend is up again. They are simply lost.

In https://redis.io/topics/notifications from "if your Pub/Sub client disconnects, and reconnects later, all the events delivered during the time the client was disconnected are lost" I understand that this is the standard Redis behavior.

Expected Behavior

The notifications are not lost but "kept" or "delayed" until an application instance is up again.

My Requests

Is this indeed the current Spring Session Redis behavior ?

Could this be fixed in Spring Session Redis ?

Are some workarounds known ?

Could this limitation be mentioned in the documentation ?

[eleftherias]

Thanks for reaching out @fbeaufume.
I've answered your question on StackOverflow.
I agree it's worth adding a warning about this limitation to the docs, similar to what Spring Data Redis does.