> 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
