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

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Coherence - Version: 3.5.3 and later   [Release: AS10g 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 0x000000005603ea50 (object 0x0000000044470000, a
com.tangosol.coherence.component.net.Cluster),
    which is held by "main"
"main":
    waiting to lock monitor 0x000000000e623390 (object 0x00000000444700e8, a
com.tangosol.coherence.component.net.Cluster$PacketPublisher),
    which is held by "PacketPublisher"
"PacketPublisher":
    waiting to lock monitor 0x000000005603ea50 (object 0x0000000044470000, a
com.tangosol.coherence.component.net.Cluster),
    which is held by "main"

Cause

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