A deadlock was detected while trying to lock a cache resource, which could be caused by unsafe use of the getBackingMapEntry() method
(Doc ID 2700689.1)
Last updated on MAY 13, 2022
Applies to:Oracle Coherence - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
A deadlock was detected while trying to lock a cache resource, which could be caused by unsafe use of the getBackingMapEntry() method. Retrying InvokeFilter request originating from members. LockContentionException in server log stating Key Contention resulted in deadlock avoidance by rolling back a thread and this
situation occurs when the concurrent invokeAlls have overlapping key sets.
There is an interceptor called xxxInterceptor on the "abc" cache. The interceptor invokes an EP called xxxProcessor and there is a getBackingMapEntry() usage, but in reality there is not a deadlock as the operation looks is automatically retried by Coherence and eventually succeeds after some time, i.e. it does not require a JVM restart just the performance is bad for some seconds/minutes.
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