BRM Memory Management Issue in PS13 Causing Signal 11's During Transitioning Purchase
Last updated on AUGUST 29, 2017
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.
On : 18.104.22.168.0 version, Subscription Management
When a client performs a transition that throws an error based on custom opcodes the dirty error buffer being passed to the PS13 (MPS1) code to do the plan purchase is crashing with a Signal 11.
e.g. Signal 11 error in cm.pinlog, see below :
The issue can be reproduced at will with the following steps:
1. Launch Customer Center
2. Open up existing customer and select the Purchase option on the Service (or Product) tab
3. Transition existing email plan from Standalone email to Regular email (free)
4. The custom code detects that the customer is not allowed to have the Regular email (free) and sets an error. This is where the error buffer becomes placed in an errored state.
5. The error is handled cleanly in PS8, but causes a Signal 11 in PS13 (MPS1).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms