You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 4, 2025. It is now read-only.
I'm trying to swap out using spring-session-data-redis for spring-session-data-mongo in a Webflux spring-cloud-gateway.
Previously with the redis implementation session information in redis was correctly auto deleted after expiry. However with the reactive mongo implementation this does not seem to be happening, and old session data remains persisted forever.
I'm using spring-boot 3.1.5, webflux, reactive mongo with Oauth2 flows in spring-security.
Could someone please clarify whether these sessions are meant to be auto-cleaned up after their expiry? I don't see any additional date-related indices on the collection when the database is autocreated.
Hi
I'm trying to swap out using spring-session-data-redis for spring-session-data-mongo in a Webflux spring-cloud-gateway.
Previously with the redis implementation session information in redis was correctly auto deleted after expiry. However with the reactive mongo implementation this does not seem to be happening, and old session data remains persisted forever.
I'm using spring-boot 3.1.5, webflux, reactive mongo with Oauth2 flows in spring-security.
Could someone please clarify whether these sessions are meant to be auto-cleaned up after their expiry? I don't see any additional date-related indices on the collection when the database is autocreated.
dependecies in pom:
Expected behavior
Expired sessions should be deleted from Mongodb
Actual behavior
Old sessions remain in Mongodb
Reactor Netty version: 1.1.12
JVM version (e.g.
java -version
): 20The text was updated successfully, but these errors were encountered: