CAS 5.1.2 Database Deadlock

[Juan Quintanilla]

Hi,

We are running CAS 5.1.2 with Oracle 12 as the backend database for ticketing/audit logs and while load testing the environment we started running into issues with the database being deadlocked.   In our oracle trace logs we are seeing the following:  

delete from TICKETGRANTINGTICKET where ticketGrantingTicket_ID=:1

In the cas logs we have the following:

2019-01-25 16:55:27,127 ERROR [org.springframework.boot.web.support.ErrorPageFilter] - <Forwarding to error page from request [/logout] due to exception [Exception thrown executing org.apereo.cas.web.flow.TerminateSessionAction@23fdf9ec in state 'terminateSession' of flow 'logout' -- action execution attributes were 'map[[empty]]']>

org.springframework.webflow.execution.ActionExecutionException: Exception thrown executing org.apereo.cas.web.flow.TerminateSessionAction@23fdf9ec in state 'terminateSession' of flow 'logout' -- action execution attributes were 'map[[empty]]'

Caused by: javax.persistence.PersistenceException: org.hibernate.exception.LockAcquisitionException: could not execute statement

Caused by: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource

It seems to only be occurring during logout requests and not does seem to happen to all the requests.  Has anyone encountered something similar with deadlocks on the Database.  

Thanks!

___________________
Juan Quintanilla

[Nathaniel Petersen]

Juan,

Where you able to identify the cause or implement a fix for this issue?  I'm experiencing a similar issue in 5.2.6.

[Juan Quintanilla]

Hi Nathaniel,

We had to disable to the defaultticketcleaner for JPA because it was not cleaning up the tickets, after disabling the cleaner we no longer experienced the Deadlock issue but we had to setup some external scripts to perform the cleanup on the tickets.

Thanks!

___________________
Juan Quintanilla

jqui...@fiu.edu

---

From: cas-...@apereo.org <cas-...@apereo.org> on behalf of Nathaniel Petersen <nathaniel...@uni.edu>
Sent: Friday, March 29, 2019 4:20 PM
To: CAS Community
Subject: [cas-user] Re: CAS 5.1.2 Database Deadlock

 

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/a9b11052-8ef5-41cb-8c7b-cba03c659ee6%40apereo.org.

[Nick Petersen]

Thanks, Juan.  That's the direction our team is moving towards.  

Doing some reading, this appears to be less an issue with CAS and more an issue with Hibernate ORM.  I need to read up more on it and how CAS implements Hibernate.  Until then, we'll probably use our own cleanup.

-Nick

--

Nathaniel N. Petersen
Systems Architect
IT - Administrative Information Systems
University of Northern Iowa 

To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/SN6PR05MB518283459A77009013AD063E86550%40SN6PR05MB5182.namprd05.prod.outlook.com.