DefaultTicketRegistryCleaner cannot find INT_LOCK table

22 views
Skip to first unread message

Pablo Vidaurri

unread,
Jul 8, 2023, 1:17:48 AM7/8/23
to CAS Community
Upgraded to CAS 6.6.8 from 6.3.7. 

cas.ticket.registry.jpa.ddlAuto=create
also tried update. 

I only see one table created: postgres_jpa_ticket_entity

but I'm getting this error:


2023-07-07 16:25:05,647 ERROR [org.apereo.cas.ticket.registry.DefaultTicketRegistryCleaner] - <Failed to lock mutex at 9a2cc683-5ea9-3212-b465-44f88885980d; nested exception is org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [UPDATE INT_LOCK SET CLIENT_ID=?, CREATED_DATE=? WHERE REGION=? AND LOCK_KEY=? AND (CLIENT_ID=? OR CREATED_DATE<?)]; nested exception is org.postgresql.util.PSQLException: ERROR: relation "int_lock" does not exist
  Position: 8
        JdbcLockRegistry.java:rethrowAsLockException:197
        JdbcLockRegistry.java:tryLock:262
        DefaultLockRepository.java:lambda$execute$1:28


I see someone else manually installed a spring scema to create INT_LOCK table but that does not seem like a CAS table.

-psv
Reply all
Reply to author
Forward
0 new messages