Unable To Release CustomerInBrmTransactionLock For The Accounts Created At The Secondary Site
(Doc ID 3075558.1)
Last updated on MARCH 11, 2025
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 15.0.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
In Elastic Charging Engine (ECE) 15.0.1.0.2 Multisite environment (Site1 - Primary and Site2 - Secondary), newly accounts created are removed from cache as CustomerInBrmTransactionLock is not getting cleared for respective Site2 accounts.
After lock cleanup interval, customerUpdater is removing the respective account from cache.
Scenario is:
1. Create a single customer which is getting created and synced to both the ECE sites (Site1 and Site2) and even in persistence DB.
2. The newly created account is getting locked in CustomerInBrmTransactionLock only at the Site2 and the actual lock never gets released.
3. After lock cleanup interval, customerUpdater is removing the respective account from cache.
NOTE:
-------
Federation is working fine from Primary to Secondary Site. A small test was done where an existing customer was deleted from ECS cache of Primary Site and observed that this particular account also got deleted from Secondary site.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |