HTTPGW NRF Retries Heart Beat at 120 Secs Instead of 60 Secs Interval During NRF Outage
(Doc ID 2940879.1)
Last updated on APRIL 20, 2023
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.7.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Elastic Charging Engine (ECE) 12.0.0.4.0, a Network Function (NRF) link failure scenario has been tested with retry counts as 60 and heartbeat timer as 60 seconds.
When the link was brought down, NRF was retrying heartbeat in every 120 seconds instead of 60 seconds. Once the link is brought up, HTTPGateway resumes heart beat interval to the correct value (60 seconds).
The gap between these 2 attempts is nearly 2 minutes:
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 |
| Cause |
| Solution |
| References |