Thanks Marvin.. Iam still in 3.3.5 - I was trying to setup 3.4.2 in Jbos but it was throwing lot of errors.. I saw your code in ExclusiveTicketRegistryCleaner.tar.gz<https://mail.google.com/secure/attachment/11460/ExclusiveTicketRegistryCleaner.tar.gz> Can i just compile that and make as part of cas-server-core 3.3.5 and change the configuration in ticketregistry.. Please tell me if iam in the right direction.. My Cas server is Cas 3.3.5 with Jboss 5. could you please suggest whatever is the easiest to make the Jdbclockingstartegy work..
Thanks Kunju On Sat, Aug 14, 2010 at 2:26 PM, Marvin Addison <[email protected]>wrote: > > But if all the node executes at the same time trying to > > select and delete . > > The Quartz job runs, sure, but the JdbcLockingStrategy code prevents > more than one node from performing cleanup at a time. If another node > runs and can't acquire the lock, it immediately exists. > > > The chances of locks are more right? > > This database-driven locking code was designed exactly to prevent > increased potential for deadlocks when multiple nodes run cleanup. > There's a lot of discussion of this both in the issue I cited and the > list archives. > > 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
