Thanks for the reply, Marvin. On Wed, Oct 7, 2009 at 10:48 AM, Marvin Addison <[email protected]> wrote: > You imply that the OOM errors started when you increased the session > timeout. There is certainly a cause-effect relationship between a 4hr > session timeout and memory usage. Please correct me if the errors do > not correlate with this change.
There are not many users logging into the system. Increasing the CAS session-timeout would mean that CAS sessions would last longer. What are the objects that are stored in a CAS session? Can you please explain the cause-effect relationship you are talking about? >> nor does it explain why the TicketRegistryCleaner is running so often. > > Based on the Spring context snippet you shared, the cleaner should run > every 83 minutes, which is clearly not the case based on the > corresponding logs. Can you tell us more about your systems > architecture; for example, are these clustered machines logging to a > single file or other repository? Also, what ticket registry are you > using? Our Apache/Tomcat server (running on a RedHat Enterprise Linux ES 4.0 machine) hosts 3 websites. CAS provides Single Sign-On service to these 3 websites. The websites access two databases (MySQL and Progress's OpenEdge). CAS uses the DefaultTicketRegistry. Thank you, Joe -- 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
