> 2014-04-17 19:51:52,279 ERROR [org.hibernate.util.JDBCExceptionReporter] - > DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=3.50.152 > > 2014-04-17 19:51:52,279 ERROR > [org.hibernate.event.def.AbstractFlushingEventListener] - Could not > synchronize database state with > sessionorg.hibernate.exception.LockAcquisitionException: could not delete: > [org.jasig.cas.ticket.TicketGrantingTicketImpl#TGT-2284-diTwnt9x0sYdKYLoXcQdWBYRb1ZTdumpbjyKK3wnHFnepuVS50-cas_25]
That error is a sign of a concurrency/locking situation. Concurrency happens; deadlocks happen; it's just a matter of usage patterns and database platform that determines the extent. I have no experience with DB2 but it may simply not handle concurrency as well as some others. Oracle does well, Microsoft SQL Server does poorly, PostgreSQL only marginally better; others can speak up about MySQL/MariaDB/whatever it's called today. I'd recommend running a cron job with a query like what I provided earlier in the thread (straight delete) and remove the Java/Quartz job and be done with it. 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
