My Oracle Support Banner

CNE: CM Pod is Getting Crashed With Exit Code 137 Frequently (Doc ID 2897423.1)

Last updated on SEPTEMBER 21, 2022

Applies to:

Oracle Communications Billing and Revenue Management - Version 12.0.0.4.0 and later
Information in this document applies to any platform.

Symptoms

Connection Manager (CM) pod in cloud native environment is getting crashed frequently with exit code 137. The user had increased the memory a number of times and scaled the CM pod to have 2 replicas, but still get frequent crashes. 
The total number accounts in the environment with the issue is 2230. The CM pod is getting crashed when multiple orders are placed at the same time and the interaction is done between Application Integration Architecture (AIA) and CM. There is an external load balancer on top of Kubernetes cluster to route the requests to worker nodes, so the request from AIA server will follow this: path AIA->LB:NodePort -> Worknode:NodePort-> CM Node Port service -> CM Pod. 


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
References


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