My Oracle Support Banner

Managed Server is Dropped Out of Cluster Due to Timeout and Never Rejoins the Cluster When Using Multicast (Doc ID 1670871.1)

Last updated on NOVEMBER 10, 2023

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Symptoms

Consider the following cluster configuration.

Heartbeats are sent from Server1 every 10 seconds (4:04:11, 4:04:21, 4:04:31, 4:04:41 etc.), but the last heartbeat sequence that Server2 received was seqNum:250 (at 4:04:21 PM EDT). When we shutdown the cluster and run Multicast test, the multicast test results are good, meaning, heartbeat messages are transferred from both nodes to both nodes correctly.

Changes

WLS 10.3 was upgraded to 10.3.6. At that time all of the clusters were on Unicast, but due to some CPU issue caused by Unicast, on Oracle's recommendation, the cluster was changed to Multicast.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.