To fix some Spring Webflow issues we were seeing, I recently beefed up a bunch of timeouts. I set the web.xml session-timeout to -1 (infinite) and changed the ticketExpirationPolicy to 120hrs. I did this last Friday (5/30).
This morning our CAS instance was down due to an OutOfMemoryException (OOME), and that's the first time this has ever happened to us. I'm wondering if leaving sessions alive too long is exposing a memory leak somewhere in CAS (I'm on 3.5.2.1)? Has anyone else ever seen this? -- 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
