How to Diagnose Healthcheck Timeouts in OpenSAFfire Enabled Applications
(Doc ID 1496387.1)
Last updated on FEBRUARY 11, 2019
Applies to:Oracle Communications OpenSAFfire - Version 6.2.0 and later
Information in this document applies to any platform.
In OpenSAFfire, Availability Management Framework (AMF) is responsible for ensuring the health of applications (represented as Components) in an OpenSAFfire environment.
AMF does this by periodically invoking a callback function in the application. A response is expected back from the component in order to deem it "healthy".
Unfortunately, it is possible for applications to get stuck or hang and fail to respond to AMF healthchecks in a reasonable timeframe. This results in AMF performing the configured component recovery action.
When analysing logs, these are the typical steps which suggest the application/component is not responding in time to AMF:
1. AMF initiates the callback to the component:
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