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
I use Jdbc session, I want to mark some sessions as expired.
So I call
//private val sessionRegistry: SessionRegistry,
sessionRegistry.getAllSessions("login", false).forEach {
it.expireNow()
}
getAllSessions returns SpringSessionBackedSessionInformation objects.
Calling expireNow on them calls super.expireNow and adds the SpringSessionBackedSessionInformation.EXPIRED attribute.
The times of the session are not touched in DB.
So far so good.
When the clean up job launches in JdbcIndexedSessionRepository it only checks the expiry date, so expired sessions are kept in db.
clean up cron should delete sessions based on expiry time but also based on the presence of the SpringSessionBackedSessionInformation.EXPIRED attribute.
The text was updated successfully, but these errors were encountered:
Describe the bug
I use Jdbc session, I want to mark some sessions as expired.
So I call
getAllSessions returns SpringSessionBackedSessionInformation objects.
Calling expireNow on them calls super.expireNow and adds the SpringSessionBackedSessionInformation.EXPIRED attribute.
The times of the session are not touched in DB.
So far so good.
When the clean up job launches in JdbcIndexedSessionRepository it only checks the expiry date, so expired sessions are kept in db.
Example data from DB :
corresponding attribute :
Expected behavior
clean up cron should delete sessions based on expiry time but also based on the presence of the SpringSessionBackedSessionInformation.EXPIRED attribute.
The text was updated successfully, but these errors were encountered: