The Diameter Control Agent Process Core Dumps logging "CRITICAL: ASSERT" When DEBUG=ALL is turned on
(Doc ID 1491181.1)
Last updated on MAY 25, 2018
Applies to:Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.
On Network Charging and Control, Version 4.4.1, the Diameter Control Agent is core dumping and is being restarted by the watchdog when all the debug flags are turned on, logging a last error message similar to this:
Sep 11 17:04:35.145608 diameterControlAgent(22837) CRITICAL: ASSERT(field == dca::CallingParty || field == dca::DestinationRoutingAddress || field == dca::RedirectingPartyID || field == dca::OriginalCalledParty) failed at INAPToAVPMapper.cc:2031
Note that the interesting part in the message above is the "CRITICAL: ASSERT".
- Using a version of the DCA binary that includes one or more assert debug satements.
- Turning DCA debug on without excluding the cmnAssert flag.
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