Customer Update Requests Fail to Publish to ECE and Lead to ECE Cluster Instability
(Doc ID 2727128.1)
Last updated on JANUARY 19, 2021
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Integration with other product
Custom change or updates from Customer Relationship Management(CRM)system are failing with -304 publish error in connection Manager/Data Manager(CM / DM).
The issue is not consistent and fails randomly, most failure are having timeout error or node failure error in emGateway.
When these error occur, ECE nodes start losing from cluster and in hung state. They re-join very long time later and meantime some customers are also lost in ECE grid.
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