My Oracle Support Banner

Coherence 3.5.3 - Deadlock When Cluster.Start Throws An Exception (Doc ID 1321079.1)

Last updated on NOVEMBER 18, 2019

Applies to:

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

Symptoms

The an exception was thrown during cluster startup resulting in a deadlock.

Found one Java-level deadlock:
=============================
"PacketListenerN":
    waiting to lock monitor xxxxxxxxxxx (object yyyyyyyyyy, a com.tangosol.coherence.component.net.Cluster),    which is held by "main"
"main":
    waiting to lock monitor xxxxxxxxxxx (object zzzzzzzzzz, a com.tangosol.coherence.component.net.Cluster$PacketPublisher),    which is held by "PacketPublisher"
"PacketPublisher":
    waiting to lock monitor xxxxxxxxxxx (object uuuuuuuuuu, a com.tangosol.coherence.component.net.Cluster),    which is held by "main"

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.