diameterControlAgent Throttles INITIAL and EVENT Requests when Throttling is Disabled
(Doc ID 2140647.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 to 5.0.2 [Release 5.0]
Information in this document applies to any platform.
In Oracle Communications Network Charging and Control (NCC) 5.0.2, throttling was added to the diameterControlAgent for INITIAL and EVENT requests to prevent the overloading of upstream processes.
At least one request has been throttled if the following error can be seen in the diameterControlAgent log:
The four parameters which control the throttle limit and reporting period are the following:
- throttleLimitError is the DIAMETER result code returned if a request is throttled. This defaults to 3004
- counterLogInterval is the period in seconds between logged throttle reports. This defaults to 600
- throttleThreshold is the number of requests received in the last throttleInterval before throttling occurs. This defaults to 0 (off)
- throttleInterval is the period of time in milliseconds which requests are counted over. This defaults to 100
A bug exists in diameterControlAgent where requests are still throttled despite throttleThreshold being set to 0 (or off).
Installation of NCC 5.0.2 and slight increases in DIAMETER traffic.
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