Deadlocks in Quartz QRTZ_LOCKS tables

Solution In Progress - Updated -

Issue

  • Our application using RHPAM and Quartz Timers reported a set of Deadlock on the Database:
2022-10-20 09:13:01 UTC-635108bc.34250-ERROR:  deadlock detected
2022-10-20 09:13:01 UTC-635108bc.34250-DETAIL:  Process 213584 waits for AccessExclusiveLock on tuple (0,2) of relation 11378148 of database 16498; blocked by process 219944.
        Process 219944 waits for ShareLock on transaction 27193750; blocked by process 208880.
        Process 208880 waits for ShareLock on transaction 27193737; blocked by process 221408.
        Process 221408 waits for AccessExclusiveLock on tuple (0,2) of relation 11378148 of database 16498; blocked by process 213584.
        Process 213584: SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = 'SpringBootScheduler' AND LOCK_NAME = $1 FOR UPDATE
        Process 219944: SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = 'SpringBootScheduler' AND LOCK_NAME = $1 FOR UPDATE
        Process 208880: update ENERGY_BPM.ProcessInstanceInfo set lastModificationDate=$1, lastReadDate=$2, processId=$3, processInstanceByteArray=$4, startDate=$5, state=$6, OPTLOCK=$7 where InstanceId=$8 and OPTLOCK=$9
        Process 221408: SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = 'SpringBootScheduler' AND LOCK_NAME = $1 FOR UPDATE

Environment

  • RHPAM 7.x
  • Spring Boot 2.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content