Brm Pin_mta: Multiple Threads Are Running, Core Mta Calls the Worker with Null Pointer
(Doc ID 1356587.1)
Last updated on AUGUST 09, 2018
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, MTA
The issue can be reproduced with the following steps:
For a custom utility which is using BRM 74 OOTB MTA framework:
When Multiple threads are running, MTA framework (core mta) sometimes calls the worker with NULL flist. We had 5 threads turned ON, and after processing around 15K records, it calls all the 5 thread (worker opcodes) with NULL flist.
The issue has the following business impact:
Due to this issue, performance of the custom mta based scripts is an issue.
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