Cm Loops Infinitely When There Is An Error
(Doc ID 1634565.1)
Last updated on FEBRUARY 22, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, CM
The user deployed PS19 to the Production last week and found an issue where cm is looping infinitely and consuming 100% CPU. The issue is happening for a billinfo update scenario. The customisation in the code prevents the billinfo update for duplicate PIN_FLD_BILLINFO_ID fields; if a duplicate is found, it returns a PIN_ERR_DUPLICATE error. However, the OOB code is not able to handle this error and loops.
This worked fine in PS14, where the process exited with the error message, but in PS19 it looks as though the error is not handled properly as the cm goes into an infinite loop while trying to handle the error and consuming 100% CPU. This is causing other issues because it is creating blocking sessions in the database and halting the whole system. The agents are not able to process orders, and the billing application hangs because of the blocking sessions. We have to manually kill the process daily to let other processes like billing to run.
cm loops infinitely when there is an error.
cm should exit when there is an error.
1. Modified fm_cust_pol_prep_billinfo.c and make fm_cust_pol_custom.so to throw an exception.
2. Created an account and try to change the BDOM through Customer Center.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|