Managed Server is Dropped Out of Cluster Due to Timeout and Never Rejoins the Cluster When Using Multicast
Last updated on MAY 01, 2018
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
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.
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.
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