My Oracle Support Banner

diameterControlAgent Throttles INITIAL and EVENT Requests when Throttling is Disabled (Doc ID 2140647.1)

Last updated on FEBRUARY 03, 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.

Symptoms

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:

Apr 20 09:40:19 slc-a diameterControlAgent: [ID 953149 user.warning] diameterControlAgent(9990) WARNING: {960157} Throttled 1 requests in the last 60 seconds.

The four parameters which control the throttle limit and reporting period are the following:

DIAMETER = {

    DCAInstances = [

        {
            DiameterServer = {

                throttleLimitError = 3004
                counterLogInterval = 600
                throttleThreshold = 0
                throttleInterval = 100

            }
        }

    ]

}

where:

A bug exists in diameterControlAgent where requests are still throttled despite throttleThreshold being set to 0 (or off).

Changes

Installation of NCC 5.0.2 and slight increases in DIAMETER traffic.

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
Changes
Cause
Solution
References


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