My Oracle Support Banner

ECE Customer Loss When Some Of ECS Nodes Stopped (Doc ID 2555555.1)

Last updated on SEPTEMBER 09, 2019

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.7.0 and later
Information in this document applies to any platform.

Symptoms

In the environment , it was observed that there was a Full GC (Garbage Collection in JAVA )for one of the node. When this Elastic Charging Server (ECS) node was manually killed leading to loss of customer information from the Elastic Charging Engine (ECE) cache. The rapid growth of Garbage collection can be observed by following the steps:


1. Create a customer with products Telephony, GPRS and SMS with same Public User ID (PUID).
2. Initiate a Sy session with above PUID, which creates Sy session for all three products.
3. Open a testnap transaction for the above customer
    Do balance updates though PCM_OP_PYMT_DEBIT to breach 3 policy lables.
4. Commit the transaction. Observe that GC is growing rapidly.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.