> The HashMapBackedSessionMappingStorage is actually storing the entire session > object in the Map.
I'm not aware of any container storage mechanism that doesn't store its contents in memory in some way, so you're in a unique situation if you really have session storage that doesn't incur any memory footprint. Since the overwhelming use case for session data is memory-backed, having a reference to it in a memory-backed map only adds another memory reference, which is negligible. In any case, you may be interested to review the patch attached to https://issues.jasig.org/browse/CASC-114. Although the default implementation stores the a reference to the Session in a memory Map, there's a JBossCache implementation that only stores the CAS Assertion in the cache. This would alleviate your problem and also give you clustered single sign out, which likely would also be of benefit to you in what appears to be a HA environment. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
