Sharing Customers: Problem Of Concurrent Accesses
(Doc ID 2193406.1)
Last updated on AUGUST 05, 2018
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 11.3.0]
Information in this document applies to any platform.
The concurrent access policy seems not managed inside ECE when it comes to sharing customers. Please refer the below use case.
1) The OCS system may have the following :
- 1 Diameter Gateway
- 2 charging nodes, ecs1 and ecs2.
- ECE 188.8.131.52.2 / Revision-Number=10463
- BRM 7.5 PS12 + patches
- PDC 184.108.40.206.0
2) Current behavior
Please refer the following scenario launched five times concurrently on two accounts which shares the same balance (sharing customers)
- 1 Spending Limit Request Initiate (SLR-I / Sy)
- 1 Credit Control Initiate (CCR-I / Gy)
The first account is the owner of the balance ("father account") and the second account access to the balance ("son account").
The majority of SLR requests on the father account are rejected (SYSTEM_ERR error) because during this time, the son is locking a resource linked with the father account.
Note: The problem of concurrent access occurs as well when launching a CCR concurrently on two sharing customers (ex: 1 father account and 1 son account).
3) Expected behavior
The concurrent access should be managed in a way that when a lock is set by an account request, all the other account's requests should wait for the lock to be released before carrying on any action or should implement a retry mechanism of the current request.
Currently, when a resource is locked by an account, the other account's requests are automatically rejected.
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