SOLVED: Coherence 3.6 problem starting two nodes on the same machine

Posted:   |  More posts about problem solved technology weblogic

I am trying to configure Weblogic 10.3.5 with Coherence cluster and two nodes. Everything is running on my local machine. I configured Coherence with WLST and now trying to run both nodes. One node starts and second fails with following exception:

2012-05-10 12:57:37.681/6.175 Oracle Coherence GE (thread=Environment.Background.Executor:Thread-1, member=n/a): Error while starting cluster: java.lang.NullPointerException at at at at at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3) at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:7) at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26) at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:2) at at at at at at at at at at at at$ at java.util.concurrent.Executors$ at java.util.concurrent.FutureTask$Sync.innerRun( at at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( at java.util.concurrent.ThreadPoolExecutor$ at

I configured servers to run on the same port and enabled Unicast Port Auto Adjust, thinking that Coherence would be smart enough to figure out that port is in use.

But it is not that smart!

But Oracle Metalink has more information about it:


Coherence 3.6 has since Patch 2 been enhancing its network throughput by using two open UDP ports for each member. For this Coherence picks Unicast listener + 1 for the second port. It has been implemented as a part of COH-3722.

Note that Coherence 3.6.1 and onwards will not have the NullPointerException but a more meaningful error message.


Separate nodes which run on the same machine by at least two ports.

For example:

When you specify localport=6000 for one node, it will also use port 6001.

The next node you can specify to use localport=6002 will also use 6003

Again the next node you can specify to use localport=6004 will also use 6005


I reconfigured Unicast ports accordingly and the problem is solved!

Contents © 2013 Aleksey Maksimov - Powered by Nikola