diameterBeClient Crashing with Memory Corruption because of Event Size
(Doc ID 2403399.1)
Last updated on MARCH 18, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
On Oracle Communication Convergent Charging Controller (OC3C or 3C) version 6.0.1, diameterBeClient is crashing with memory corruption because of event size.
Customer is experiencing diameterBeClient coredumping for some cases of Balance Query to Elastic Charging Engine (ECE).
Due to Diameter Charging Driver crash, all communication with ECE are impacted.
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