Correct Behavior of "-Dcoherence.localport.adjust=false" Option in Coherence 12.2.1.x (Doc ID 2127922.1)

Last updated on OCTOBER 09, 2023

Applies to:

Symptoms

Unlike earlier versions two cache-servers can be started even though the "-Dcoherence.localport.adjust=false" option is set in the configuration for 12.2.1.0.0 version.

Changes

The behavior was changed from Coherence 12.2.1.x when the "-Dcoherence.localport.adjust=false" option is used.

• Coherence 12.2.1.x:

1. 1. The "-Dcoherence.localport.adjust=false" is not reflected if the "-Dcoherence.localport=<port>" is not set. It should be used with "-Dcoherence.localport=<port>".
   2. Only one cache server can be started when the "-Dcoherence.localport.adjust=false" is used with the "-Dcoherence.localport=<port>". Other cache servers cannot be started on the same machine.

• Before Coherence 12.1.3.x:

1. 1. Only one cache server can be started when the "-Dcoherence.localport.adjust=false" is used regardless of whether the "-Dcoherence.localport=<port>" option is used or not on a machine with specific IP is set to localhost or to WKA address.

    

   Note: In the 12.2.1 release the command-line properties are changed to coherence.* from tangosol.coherence.* However the old notation is still valid.

    

Cause

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