CNE: CM Pod Is Not Coming up if pcm_timeout_in_msecs Is Used
(Doc ID 2829783.1)
Last updated on AUGUST 19, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
In any version of BRM (Billing and Revenue Manager), pcm_timeout_in_msecs parameter is used to configure multilevel CM (Connection Manager) timeout for client requests. When this timeout period expires, the CM returns a PIN_ERR_TIMEOUT error to the client. In a high-availability system with multiple Data Managers (DMs) configured, the CM connects to the secondary DM to process the requests. Documentation Link: [https://docs.oracle.com/en/industries/communications/billing-revenue/12.0/sys-admin/monitoring-connection-manager-activity1.html#GUID-1B1B93DC-CE83-4D7C-B6EC-EA470C2902CC]
In a Cloud Native Environment (CNE), Connection Manager (CM) POD is not coming up if pcm_timeout_in_msecs parameter is added in configmap_pin_conf_cm.yaml file.
The container is getting waiting state forever.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |