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

Last updated on MAY 30, 2016

Applies to:

Oracle Coherence - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

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.

    1. The "-Dtangosol.coherence.localport.adjust=false" is not reflected if the "-Dtangosol.coherence.localport=<port>" is not set. It should be used with "-Dtangosol.coherence.localport=<port>".
    2. Only one cache server can be started when the "-Dtangosol.coherence.localport.adjust=false" is used with the "-Dtangosol.coherence.localport=<port>". Other cache servers cannot be started on the same machine.
    1. Only one cache server can be started when the "-Dtangosol.coherence.localport.adjust=false" is used regardless of whether the "-Dtangosol.coherence.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

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