My Oracle Support Banner

Cloud Native ECE is not Getting Started Due to Not able to Connect to Coherence (Doc ID 2770725.1)

Last updated on OCTOBER 28, 2021

Applies to:

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

Symptoms

The user is  on Cloud Native Billing and Revenue Management (BRM) 12.0 Patch Set (PS3) with Elastic Charging Engine (ECE) and Interim Patch 4 (Patch 32078697)
ECE pods were up and running fine after initial environment setup. After a few days, the user was unable to do /query.sh as it was taking a long time and eventually timed out. Upon checking the ECE logs, it is unable to establish connection with Elastic Charging Server (ECS) nodes, and all ECS pods are not connecting to Coherence.

ECE Java Management Extensions (JMX) node is stuck with below message and getting timeout after few minutes.

ERROR
-----------------------

 

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


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