Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

TICKETGRANTINGTICKET table is getting "Locked" CAS 3.5.2

Description

TICKETGRANTINGTICKET table is getting "Locked" when there are multiple users are Idle. We found that the below query is causing the Locks :

select ticketgran0_.ID as ID1_0_, ticketgran0_.NUMBER_OF_TIMES_USED as NUMBER2_1_0_, ticketgran0_.CREATION_TIME as CREATION3_1_0_, ticketgran0_.EXPIRATION_POLICY as EXPIRATION4_1_0_, ticketgran0_.LAST_TIME_USED as LAST5_1_0_, ticketgran0_.PREVIOUS_LAST_TIME_USED as PREVIOUS6_1_0_, ticketgran0_.ticketGrantingTicket_ID as ticketG10_1_0_, ticketgran0_.AUTHENTICATION as AUTHENTI7_1_0_, ticketgran0_.EXPIRED as EXPIRED1_0_, ticketgran0_.SERVICES_GRANTED_ACCESS_TO as SERVICES9_1_0_
from casadmin.TICKETGRANTINGTICKET ticketgran0_
where ticketgran0_.ID=:1 for update;

Please treat this as Urgent as we are facing this issue in Production Environment.
We have already created the Index and tried disabling the Quartz job but nothing helps.

Environment

Linux operating systema and CAS is running on Apache Tomcat 7.

Activity

Show:

Misagh MoayyedJuly 24, 2015 at 2:36 PM

First, JIRA is no longer used for the CAS project. Please use Github issues.

Second, this is sort of a known problem with the JPA ticket registry and we no longer recommend folks use it. Your best alternative would be to use a cache-based ticket registry. I don't think the CAS project plans to maintain that registry any longer.

Fixed

Details

Assignee

Reporter

Labels

Original estimate

Time tracking

No time logged3m remaining

Components

Affects versions

Priority

Created July 23, 2015 at 8:25 AM
Updated July 24, 2015 at 2:36 PM
Resolved July 24, 2015 at 2:36 PM

Flag notifications