ECE Thread Prioritization For Online Orders And Better Retry Handling
(Doc ID 2717786.1)
Last updated on OCTOBER 08, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On Oracle Communications Elastic Charging Engine (ECE) 188.8.131.52.0 version, Customer data management
ECE thread prioritization for online orders and better retry handling
Currently when there is a backlog processing/high volume of input for any individual or sharing account, the entry processor threads for subsequent usage processing requests and the online orders are waiting/queued up for acquiring the lock before further processing. Since online orders have direct customer impact and impact to multiple systems, it would be good to allow prioritization of these threads/jobs over usage processing. Better to have this configurable.
Currently if the entry processor is not able to acquire the lock, without waiting on a event notification when the thread is freed up, it continuously spins around for the configured number of times which is an overhead on the CPU/resources. Since online orders have direct customer impact and impact to multiple systems, it would be good to allow prioritization of these threads/jobs over usage processing. It would allow lesser operation interference and customer complaints
Currently the Product doesn't allow any prioritization of the threads for online orders vs usage processing.
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