My Oracle Support Banner

FMW WLS Domain Coherence Cluster Transport Protocol Options Change Causing Startup Failures after Patching or Upgrading with Additional Port Use. (Doc ID 2919191.1)

Last updated on FEBRUARY 16, 2024

Applies to:

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

Purpose

Fusion Middle Ware WebLogic Server Coherence Cluster Configuration Transport Protocol Options have changed in the 12.2.1.4 and 14.1.1.0 versions that is causing the server startup failure after patching to the latest patch to these versions or upgrading from the previous versions. The below section helps to understand the changes and steps to implement to keep the working functionality or change the protocol as when needed for the better larger coherence cluster stability.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 What changed in the Patch/CPU Release?
 What is the Default Transport Protocol in the previous releases and later the patch?
 What is the recommended Transport Protocol to use for the 12.2.1.4 or 14.1.1.0 Coherence Cluster in the FMW WLS Domains?
 What type of issue would affect the server start in the domain after Patching or after Upgrade?
 Why am I seeing server startup failures even after TMB is set in the admin console for the Coherence Cluster?
References

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