-
Feb 6th, 2013, 03:25 PM
#1
Bug when expiring session with non-in-memory SessionRegistry (concurrent sessions)?
In ConcurrentSessionControlStrategy, when expiring the least recently used session, expireNow() is called on the SessionInformation object, but nothing is done to persist this to the SessionRegistry. This works fine for the default, in memory, SessionRegistry implementation, but, with a non-in-memory implementation, it appears that the session will never be expired in the registry. In fact, there is no interface on the SessionRegistry which would allow this to be persisted. Am I missing something, or is this an oversight?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules