Please forgive me if this problem has been raised on the list previously - I 
can't seem to access the archives for this list further back than a week or two 
through the web interface?

We are running CAS 3.4.12 with JpaTicketRegistry storing our tickets in an SQL 
Server 2012 database.  We have been experiencing deadlock issues.  We did 
disable the TicketCleaner (and instituted a nightly purge of old TGT and STs 
via T-SQL), but the issue persists.  Recently, we enabled the 
READ_COMMITTED_SNAPSHOT option on the database - which seemed to help, but has 
not eliminated the log messages completely.  I was wondering if there is anyone 
else using SQL Server 2012 specifically who could offer advice on this?

We have been thinking of enabling snapshot isolation 
(http://msdn.microsoft.com/en-us/library/ms188277.aspx), or switching away from 
JpaTicketRegistry entirely.

Thank you,
Curtis Long

Unix Administrator
Durham College
T:  905-721-2000 x2714
C:  905-261-8337




-- 
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

Reply via email to