Thanks, I was afraid you were going to say that. It's interesting that we never had any deadlocks on MySQL when we were running on a single server. I just don't have the time resources or expertise to build out a highly-available MySQL cluster and maintain it.
Incidentally, I saw the JIRA from a couple years ago that got marked as resolved after you merged a patch. Is there anything I can provide that would make it worthwhile to reopen it? Geoff -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Tuesday, October 21, 2014 9:12 AM To: [email protected] Subject: Re: [cas-user] CAS 3.5.2 - SQL Deadlocks - Not cleanup related > Can anybody shed some light on this, please? Any thoughts on where to look? It's a known issue and there's little remedy. Searching the list archives you'll find that deadlocks are most commonplace on MSSQL. We've tried several fixes to reduce the likelihood of deadlocks, but nothing short of an API change will solve the problem in a truly satisfactory manner. I would recommend a cache-based ticket registry like memcached, Ehcache, or Hazelcast. I will say that many folks have achieved performance with acceptably low deadlock rates with JpaTicketRegistry on other database platforms. I have personal experience with PostgreSQL and Oracle, and both performed acceptably well. 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
