Hello, We are using CAS 3.2.1 and are exploring the different ticket registry implementations that are available for clustering CAS. Could you please guide me as to what factors (pros/cons) are existing for each of the ticket registry. (Memcache, JbossCache, JPATicketRegistry) . Any performance metrics available for them serving as basis of comparison?.
I understand that by changing the scope of the transaction (for getTickets/deleteTickets method) has resolved the issues related to deadlock faced in JPATicketRegistry. Thanks, Shivani On Mon, May 11, 2009 at 8:23 PM, Marvin Addison <marvin.addi...@gmail.com>wrote: > > Regarding the performance issue, what if the transaction were limited to > > reading a single Ticket and deleting it if it's expired? > > I started leaning toward this sort of solution, but first I had to be > able to reproduce the problem in my environment. I was able to do > that and I created http://www.ja-sig.org/issues/browse/CAS-782 and > attached a number of helpful resources, including a patch that solved > the problems in my environment. Please review and comment. I'm > particularly interested in feedback regarding how the suggested patch > might impact other ticket registry implementations. > > Regards, > M > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > shivani.chan...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
