CM Takes 75s to Detect Endpoint Failure on HPUX Systems
(Doc ID 2706985.1)
Last updated on SEPTEMBER 08, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On all versions if Oracle Communications Billing and Revenue Management (BRM), if the host where the endpoint that the Connection Manager (CM) is talking to goes down, it can take up to 75s for CM to detect this failure.
During this time, the CM in question does not process any other requests and eventually logs the errors:
In this particular example, CM is connecting to the External Manager Gateway (emGateway) running on Oracle Communications Elastic Charging Engine (ECE).
To reproduce this issue:
1. Configure CM to query ECE via the emGateway endpoints in a High Availability (HA) setup
2. Connect to CM via testnap and call the PCM_OP_BAL_GET_ECE_BALANCES opcode with the appropriate input flist
3. Stop the host where emGateway is running
4. Rerun the opcode from Step 2
This issue only affects Hewlett Package Unix (HP-UX) operating systems (OS).
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