Memory Leaks Detected in the Invoicing Code
(Doc ID 1633786.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
Using Valgrind Memcheck tool to detect memory issues, three memory leaks have been discovered in the invoicing code of the Billing and Revenue Management (BRM) software version 7.5 PS4.
This problem happened in the standard invoice generation, hence the scenario was very much standard :
- Create an account
- Purchase a product with Monthly Cycle Arrear and a purchase fee
- Move the PIN Virtual Time to the next appropriate date to be able to run billing
- Run billing
- Run Invoicing with Valgrind or any other tool to detect memory leaks
Running CM with Valgrind
- Add the following entry in the CM pin.conf
It is expected that no memory leak should happen with the BRM OOB code.
This problem happened with BRM 7.5 PS4.
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
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.