> > When I got a heap dump I was shocked to see that there were tickets in > there which took close to 10Mb of memory (deserialized). After > investigation this was pretty much all allocated in the 'services' map that > is stored in the TGT. >
This is a known issue and a great example of why we need to tighten up the storage model in future versions of CAS. We hold on to way more data than is needed to track accessed services (needed for logout). That said, despite improvements and optimizations, it's not unreasonable to expect problems from an SSO session that tracks service sessions for 90 days. We might want to expose a configuration knob to turn off session tracking since the only case for that is SLO, which is meaningless over a span that long. It seems like you pretty much came to a similar conclusion on your own. You might reframe your problem as a design suggestion and discuss further on cas-dev. 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
