When I was at RU, we also never had any emergency memory outages. It was more likely that we rebooted because of an upgrade or a patch to the OS than because of an actual issue with CAS. In terms of overall uptime, I'd have to ask someone at RU.
On Mon, May 9, 2011 at 2:59 PM, Marvin Addison <[email protected]>wrote: > We've never had an emergency restart of CAS due to resource usage or > below average response times. The only restarts we do are on > redeploys or other misc config changes, which happen on the average of > every 6 months. > > > We had a typo in our ticket expiration policy so they didn't time out for > > 100 hours. We have 2.5 gigs of memory allocated to CAS and were garbage > > collecting every few moments because we would run down to 35 meg free > space. > > Seems you'd have reached your steady state memory usage well before > now if it were related to number of SSO sessions (due to long > timeouts). I'd look around some more. > > 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 > > -- 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
