Hi Marc, Many thanks for clearing that up.
-lucas On May 24, 2007, at 6:43 AM, marc antoine garrigue wrote: > > > > My first question: If I am using the JBossCacheTicketRegistry, do I > have to implement a custom RegistryCleaner (which is alluded to here: > http://www.ja-sig.org/products/cas/server/cluster/index.html )? > > You would most likely just want to ensure the default registry is > only running > on one of the machines in the cluster (as cleaning on one should be > propagated > to the others). > > So, you are saying I would have to comment out the registry cleaner > for all but > one of the hosts? > > <quote> >>> My first question: If I am using the JBossCacheTicketRegistry, do I > have to implement a custom RegistryCleaner (which is alluded to here: > http://www.ja-sig.org/products/cas/server/cluster/index.html )? > >> You would most likely just want to ensure the default registry is >> only running > on one of the machines in the cluster (as cleaning on one should be > propagated > to the others). > > If so, I will have to do a post-deployment config change as I am > "blindly" > moving my cas.war file out to our hosts. > </quote> > > Hi Lucas, > In fact you can run the default RegistryCleaner on each node, this > is not a > problem since you use a synchronous replication configuration of > JbossCache that > does not allows the same ticket to be cleaned once (to be perfectly > write this > is really true when you use a transactional replication, but even > with four > nodes in synchronous replication mode collision has very low > probability to > happen). This strategy will cluster the registry cleaning task. > > Hope this helps > > Best regards > MAG > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
