> 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? >
Several folks have reported issues with SQL Server deadlocks, but I have not received any data to help investigate or remediate the problem. I need deadlock traces that show what resources the two sessions are deadlocked on. Please provide that if you can. The more data we have the better. Today we have nothing helpful other than general problem descriptions. 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
