OIPA/Cycle Deployed Under TomEE Unable to Join Coherence Cluster When Using 2+ Instances (Doc ID 2909547.1)

Last updated on NOVEMBER 15, 2022

Applies to:

Symptoms

On : 11.3.1.9 version, Cycle Issues

OIPA/Cycle is unable to join the Coherence Cluster when using 2+ instances on different servers on TomEE.
Configure 2 instances of OIPA deployed on separate servers and when attempting to join the same Coherence Cluster,
the following error message is reported:


ERROR
-----------------------
Delaying formation of a new cluster; unicast networking appears to be inoperable on interface XX.XX.XX.XX as this process isn't receiving even its own transmissions; consider switching network interfaces



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install OIPA 11.3.1.X on TomEE on 2 different servers.
2. Configure each server set to join the same Coherence Cluster.
3. On startup of the servers notice that they do not join the Cluster and Coherence outputs issues.

Launch OIPA or Cycle stand alone with only 1 respective node, both will start and work as expected.
Able to fully use the UI or run batches. The issue occurs when attempting to have 2 instances in the same Cluster.

They have confirmed all ports are open and accessible between the 2 servers.
If Cycle Agent & Cycle Client are on the same server, they can join the Coherence Cluster w/o issue however when trying to add in another server, the same issue is encountered.

Cause

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