SOA/BPM 12c Servers are Failing to Create a Coherence Cluster While Deploying the OracleBPMBACServerApp and BPMComposer Applications
Last updated on JUNE 28, 2017
Applies to:Oracle Coherence - Version 220.127.116.11.0 to 18.104.22.168.4 [Release 12c]
Information in this document applies to any platform.
The following errors are reported in the the instance's standard out log file, while starting a SOA server in a SOA/BPM cluster:
Oracle SOA Suite 12c utilizes an embedded Coherence cache to coordinate several cluster-wide activities, including composite deployment. As a result an in-process coherence cluster is created while starting the SOA/BPM cluster. In environments where there are hosts with multiple subnets/VLANS/infiniband-links, such as Exalogic, it is possible for this error to be encountered while the SOA/BPM applications are deploying.
As part of the SOA managed coherence server there is an additional Coherence instance started by each OracleBPMBACServerApp and BPMComposer application. When the BPM application's in-process coherence instance binds to an address:port combination that cannot communicate with the other instances in the cluster (the SOA/BPM/WSM managed coherence servers), the instance would wait to receive cluster heart beats from siblings until the cluster join start-up timeout has elapsed. Once the timeout has elapsed, the above errors are seen and then the SOA servers are moved to a failed state.
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