Hal, thanks for taking the time to carefully review some of the fixes slated for 3.3.3.
> I am also using the JPATicketRegistry with Oracle and getting lots of > deadlock detected exceptions in the logs. We customized the webapp to handle > the errors and there doesn't seem to be performance penalty b/c Oracle > detects the problem quickly, but it is nice to see that get fixed. I am > looking forward to the 3.3.3 release. We'd be very interested in your commenting on http://www.ja-sig.org/issues/browse/CAS-782 about your experience with the fix for that issue that should appear in 3.3.3. External verification is good even if it's after the fact. M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev