SLEE Event Corruption with Error "Memory corruption because event size X is too big for list event size 1024" (Doc ID 1903413.1)

Last updated on JULY 14, 2014

Applies to:

Oracle Communications Network Charging and Control - Version 4.4.0 and later
Oracle Solaris on SPARC (64-bit)

Symptoms

In all versions of Network Charging and Control (NCC), the potential exists for the Service Logic Execution Environment (SLEE) to be corrupted when a SLEE process attempts to write a SLEE message into an event which is too small (eg. a >1kB message into a 1kB event).

When this happens, a message similar to the following may be observed in the messages log file:

May 8 09:20:50 SLC01 slee_acs: [ID 848595 user.crit] slee_acs(4382) CRITICAL: SleeEvent::validateEvent() [this=0x83277cc8 myCurrentList=0x0 owningProcess=4382]: Memory corruption because event size 1272 is too big for list event size 1024

This will be likely followed by a core file from the offending SLEE process and a corrupt SLEE which will require manual intervention to restore (manually performing a SLEE restart).

Changes

New services added and/or new service logic on a Service Logic Controller (SLC).

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