My Oracle Support Banner

Coherence Deadlock Was Detected While Trying To Lock A Cache Resource By getBackingMapEntry() method (Doc ID 2513759.1)

Last updated on MAY 05, 2021

Applies to:

Oracle Coherence - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

A customer has reported that Entry processors (EP) are heavily used and in some cases, the EPs are invoked using filters instead of keys. At some point due to filter usage, a lock is held for the whole backingMap instead of per partitions. Federated Interceptor is trying to hold a lock, which is leading to a lock conflict between Federated Caching Interceptors and Entry Processors. A deadlock was detected while trying to lock a cache resource using getBackingMapEntry() method. Below is the error:

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.