NullPointerException In TcpRing.ensureSelector When port-auto-adjust=false And Another Node Running On The Same Machine Is Using The Next Highest Port As This Node
(Doc ID 1263748.1)
Last updated on APRIL 27, 2023
Applies to:
Oracle Coherence - Version 3.6.0 and laterInformation in this document applies to any platform.
Symptoms
There are multiple Coherence nodes configured to run on the same machine all with tangosol.coherence.localport.adjust=false.
For example:
| Node | tangosol.coherence.localport |
|---|---|
| Node 1 | 6000 |
| Node 2 | 6001 |
Node 1 can be started with no error, but on trying to start Node 2 the following exception is reported:
Trying with different port combinations for Node 1 and Node 2 gives different results:
6000/6001 -- fails
6600/6601 -- fails
6000/6601 -- works
6600/6001 -- works
6000/6002 -- works
6600/6602 -- works
Changes
This used to work fine until Coherence 3.6.0 Patch1, but is failing in Coherence 3.6.0 Patch2 and later.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |