My Oracle Support Banner

Retry Behaviour of PricingUpdater is not Similar to that of CustomerUpdater (Doc ID 2391889.1)

Last updated on MAY 11, 2018

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


On Oracle Communications Elastic Charging Engine(ECE), version,

Retry behavior of Pricing Updater (PU) should be made similar to Customer Updater (CU). Currently it is trying 19 times by default.

Retry behavior of Pricing Updater (PU) should match with that of Customer Updater (CU) since both are part of Elastic Charging Engine.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.