Hi Dave! We have the same configuration for all nodes. The cleaner is scheduled to run 20 seconds after the application starts and then periodically once per hour (the original value is greater than that: 5000 s).
Because we don’t start the nodes at the same time, the cleaner also runs at different time on different nodes. We don’t do any locking or anything like that. I think that the cleaner simply removes some tickets locally and then the deletions get replicated to other nodes, so they are in fact deleted on those other nodes too. But I don’t know the implementation, so I may be wrong on this. We introduced the cleaner quite recently, so unfortunately I have very little real experience it. Should I found something more concerning the cleaner, I will post it to this list. Best Regards, Jarda From: David A. Kovacic [mailto:[email protected]] Sent: 20. November 2014 4:56 odp. To: [email protected] Subject: Re: [cas-user] CAS 4.0.0 Production Issue: Heap Memory Issue Hi Jaroslav, Well, given the error I knew it had to be something like that - I just couldn't find where logoutManager was supposed to be defined. Thanks for pointing me in the correct direction. :-) A couple last questions on your setup: Are you running the ticket cleaner on multiple nodes of your environment simultaneously, or just one? If you run multiple simultaneous cleaners are you doing any kind of locking on the cache to prevent them from stepping on each other, or has it never been a problem for you? Thanks, Dave Join IDC beginning October 29, 2014 through January 29, 2015 for: IDC's 2015 Predictions and IDC FutureScapes Web Conference Series<www.idc.com/predictions2015> Accelerating Innovation on the 3rd Platform Register Now<http://event.on24.com/r.htm?e=861361&s=1&k=223AFC21785863D975C9D80CEE2A97C2> -- 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
