CNE - CM Pod Hangs and Liveliness Probe Becomes Unresponsive As Testnap is Unresponsive
(Doc ID 3030249.1)
Last updated on JUNE 23, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.8.0 and laterInformation in this document applies to any platform.
Symptoms
In a Billing and Revenue Management (BRM) cloud native environment (CNE), the user observes that connection manager (CM) is restarting as liveliness probe becomes unresponsive and testnap is not giving any response.
This leads to very high count of CM child processes and testnap processes to be spawned, which eventually making the load on worker node very high.
ERROR
------------------
In dm.pinlog
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 |