Memory Leaks Detected in the Invoicing Code (Doc ID 1633786.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

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 :

  1. Create an account
  2. Purchase a product with Monthly Cycle Arrear and a purchase fee
  3. Move the PIN Virtual Time to the next appropriate date to be able to run billing
  4. Run billing
  5. Run Invoicing with Valgrind or any other tool to detect memory leaks

Running CM with Valgrind

  1. Add the following entry in the CM pin.conf


    It is expected that no memory leak should happen with the BRM OOB code.

     

    Changes

    This problem happened with BRM 7.5 PS4.

    Cause

    Sign In with your My Oracle Support account

    Don't have a My Oracle Support account? Click to get started

    My Oracle Support provides customers with access to over a
    Million Knowledge Articles and hundreds of Community platforms