Messaging Manager Only Logs Load Reports when Processing Traffic
(Doc ID 2419683.1)
Last updated on AUGUST 21, 2020
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 to 18.104.22.168.0 [Release 6.0 to 12.0.0]
Oracle Communications Network Charging and Control - Version 4.3.0 to 22.214.171.124.0 [Release 4.3 to 12.0.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to and including 126.96.36.199, Messaging Manager (MM) will only log the following load report message when processing new traffic:
In very low traffic deployments, this can cause issues with monitoring tools which are only checking for the last time this message was logged and using the reported value as the current traffic rate.
For example, across 2 load reporting periods (XMS.xmsTrigger.loadReportPeriod in the eserv.config file), if the traffic drops from a high value to 0, then the last reported load will be the maximum value and an updated load report is never logged so it appears as though xmsTrigger is still handling this level of traffic (as there is no incoming traffic).
This affects the Oracle Application Management Pack (AMP) plugin for NCC/3C.
In practice, this issue will only affect testbeds or production servers taking no traffic as live servers will typically have incoming Short Message Service (SMS) messages at a reasonable rate.
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