Memory Leak Behavior In Pcm_op_gsm_aaa_authorize

(Doc ID 805097.1)

Last updated on JUNE 13, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version:
Information in this document applies to any platform.


There appears to be a memory leak in the PCM_OP_GSM_AAA_UPDATE_AND_REAUTHORIZE opcode (and possibly in the PCM_OP_GSM_AAA_AUTHORIZE opcode as well).

From the input flist to our custom opcode, the customer pulls off the PIN_FLD_VERIFY_BALANCE value and stores it in a local variable of type int *.

Before the call to the PCM_OP_GSM_AAA_UPDATE_AND_REAUTHORIZE opcode, the customer makes a copy of the input flist and pass the copy to the AAA opcode.

After the opcode returns, the value of the local variable has been changed although the value in
the flist is still correct.

The value does not get altered every time and turning on full debug logging in the cm_aaa seems to
prevent the issue from occurring.

The customer has seen similar behavior in the PCM_OP_GMS_AAA_AUTHORIZE opcode call as well but have not been able to reproduce this one while we had the extra logging output to the cm_aaa.pinlog.


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