Unicast Broadcast Channel Within Dynamic Cluster Breaks Session Replication Feature
(Doc ID 1940129.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 12c]
Information in this document applies to any platform.
***Checked for relevance on 19-Dec-2014***
When running a cluster-aware application on a dynamic cluster using a Unicast broadcast channel, the session replication feature is broken. You will be able to verify this behavior by following these steps:
- Check the session created. Each session will look similar to:
This shows that every server considers itself as senior and only sends heartbeats. As for the primary server, in the absence of remote groups, it considers itself to be alone and defaults to NONE as secondary JVM ID.In other words, cluster communication is broken and as a consequence of it, session replication no longer works.
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