Cluster Hangs After Network Failure and has to be Restarted to Restore Functionality
(Doc ID 1513706.1)
Last updated on FEBRUARY 16, 2021
Applies to:
Oracle Communications Service Broker - Version 6.0.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
On OCSB 6.0.0.1.0 calls continue to fail after the network has recovered from a temporary fault. This can occur with certain node configurations:
- 2 PN and 2 SSU cluster domains are co-located and configurations are stored in a shared file system.
Looking in the logs files, errors appended related to the Coherence instance that has been automatically stopped and restarted on PN1 and SSU1:
Changes
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 |