Packet Speaker Thread in a Coherence Node Can Become Blocked Trying to Lock a java.lang.DatagramPacket When Using either Java 7u80 or Java 8u40 and Later
Last updated on NOVEMBER 03, 2016
Applies to:Oracle Coherence - Version 220.127.116.11.0 to 18.104.22.168.2 [Release 12c]
Oracle Coherence - Version 22.214.171.124.0 to 126.96.36.199.4 [Release 12c]
Information in this document applies to any platform.
Issue encountered when running Coherence 188.8.131.52.x (where x=0,1,2,3,4) and 184.108.40.206.y (where y=0,1,2) and either Java 7u80 or Java 8u40 and higher, and the cluster is configured to use multicast and not well-known addresses (WKA) as the cluster discovery mechanism.
When the issue occurs a thread dump will show that either the publisher or speaker thread is waiting to lock an instance of java.net.DatagramPacket, which is not locked by any other thread, for example:
As a consequence of this other nodes will report communication issues with the node, potentially leading to its ejection 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