Whats your DB and CAS Server version? Send your pool settings please. With CAS 3.x, all tickets need to be deserialized to figure out which ones are expired. But your problem seems to be connection pool settings related.
> Am 27.10.2013 um 11:47 schrieb "David" <turner.da...@williamhill.com>: > > Hi, > > We are getting a CAS ticket cleanup problem - the connection is closed. I > have confirmed the JDBC connection pool settings and the pool manager will > reclaim connections after 600 seconds so I suspect the database or network > are at fault. > > We are using the JPATicketRegistry across a TC cluster - locking worked fine > but when there are a large number of tickets to clean the connection closed > issue occurs. Why does the CAS app need to take so long to clear down the > ticketgranting table? Surely it can execute a delete from where SQL statement > and use a predicate to determine if the ticket should be purged or not. Why > the need to load into memory? This is a perf overhead IMO. > > Any insight into this or if other have experienced similar problems - greatly > appreciated > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > robertoschw...@googlemail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > <TicketCleanupException_DBConnection.txt> -- 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
