Correct Behavior of "-Dcoherence.localport.adjust=false" Option in Coherence 12.2.1.x
(Doc ID 2127922.1)
Last updated on SEPTEMBER 24, 2020
Applies to:Oracle Coherence - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Unlike earlier versions two cache-servers can be started even though the "-Dcoherence.localport.adjust=false" option is set in the configuration for 18.104.22.168.0 version.
The behavior was changed from Coherence 12.2.1.x when the "-Dcoherence.localport.adjust=false" option is used.
- Coherence 12.2.1.x:
- The "-Dcoherence.localport.adjust=false" is not reflected if the "-Dcoherence.localport=<port>" is not set. It should be used with "-Dcoherence.localport=<port>".
- 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:
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.
- 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.
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