Brian, Do you have the entire stack trace? Can you send it to me, or open a ticket for it? Its possible that for some reason the page was refreshed and the same ticket was "deleted" twice which in JPA might not be a good thing. We may need to catch that in delete and swallow that exception.
Thanks Scott On Tue, May 12, 2009 at 6:35 AM, Pieslak, Brian <[email protected]> wrote: > We have deployed CAS 3.2.1 into production (and its been working > beautifully). > I have CAS configured to persist tickets to a MySql database to support > Single Sign Out. > > Yesterday a user reported seeing an error after they logged out, and the > screenshot they sent shows the following exception: > > ======= > HibernateOptimisticLockingFailureException : Batch update returned > unexpected row count from update [0]; actual row count: 0; expected 1; > ======= > > I'm not exactly sure what could have caused that exception, since I don't > have any other code that would be modifying the CAS ticket tables in my > MySql database. Is there a way to supress this exception without having > to change any compiled code? > > I see in the full stack trace a call to > org.jasig.cas.CentralAuthenticationServiceImpl.destroyTicketGrantingTicket, > and I was thinking if need be, and I was thinking that I could extend that > class and just wrap that call in a Try/Catch to supress that exception - but > that's a bit brute-force. > > Any thoughts? > Thanks, > -Brian > > > > -- > 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
