Cluster Hangs After Network Failure and has to be Restarted to Restore Functionality

Cluster Hangs After Network Failure and has to be Restarted to Restore Functionality (Doc ID 1513706.1)

Last updated on OCTOBER 10, 2016

Applies to:

Oracle Communications Service Broker - Version 6.0.0.1.0 and later
Information in this document applies to any platform.

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:

	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