Am 25.07.2011 um 15:48 schrieb Marvin Addison: > > >> This could lead to a problem because the cleaner currently locks your ticket >> registry for a long time as all tickets are deserialized. > > There is no such locking explicitly in the code, and it's hard to > imagine how _any_ database platform would lock entire tables to > perform row-level deletions in a way that would appear to lock the > entire registry.
Correct. Due to the design of deserializing all tickets in the registry, this might take a lot of time. > >> You can get java.sql.BatchUpdateException: Lock wait timeout exceeded; try >> restarting transaction exceptions due to this. > > I believe this is simply one manifestation of a deadlock, which is a > known issue with the current JPA implementation. Some platforms > handle deadlocks better than others; based on my experience Oracle is > among the best and PostgreSQL among the worst. What's your experience with MySQL? Thats the one we see the issue. > It's doubtful it will be better until there are API changes, which > are due in the CAS 4.x timeframe. > Full ack. I think with direct finders in 4.0 on expired tickets this will be resolved. Thanks, Robert -- 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
