DiameterBeClient Crashing with Memory Corruption because of Event Size

(Doc ID 2403399.1)

Last updated on MAY 31, 2018

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communication Convergent Charging Controller 6.0.1 version, 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.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms