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

Last updated on MAY 22, 2023

Applies to:

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

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