Coherence Distributed Cache Service Hangs On Lock Due To Mix Of Using Direct Backing Map Access And BackingMapContext.getBackingMapEntry API.

(Doc ID 2214163.1)

Last updated on JANUARY 29, 2017

Applies to:

Oracle Coherence - Version to [Release 12c]
Information in this document applies to any platform.


In the Oracle Coherence Cluster Distributed Cache Service is hanging on locks. The scenario is soft timeout(s) on one member of a cluster shows two threads of a distributed service hanging on a lock while all other threads are idle, overnight other threads also got blocked. Customer has killed the service on the node and in the process of re-balancing of the distributed cache partitions another node got ejected from the cluster.



Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms