xmsTrigger Logging an Error "Sleeevent:: Memory Corruption Because Event Size 1032 Is Too Big For List Event Size 1024"

(Doc ID 1365990.1)

Last updated on MARCH 27, 2015

Applies to:

Oracle Communications Network Charging and Control - Version: 2.2.0 and later   [Release: 2.2 and later ]
Information in this document applies to any platform.

Symptoms

xmsTrigger, the core process of Xtreme Msg (MMX) application handling the text messages on the Service Logic Controller (SLC) is regularly core dumping for an unknown reason, logging the following kind of error message in the system's syslog :

The system's syslog is generally located at /var/adm/messages


Oct 5 08:05:51 slc01 xmsTrigger: [ID 848595 user.crit] xmsTrigger(13690) CRITICAL: SleeEvent::validateEvent(): Memory corruption because event size 1032 is too big for list event size 1024


There is an user impact as xmsTrigger corrupts the shared memory and needs to be restarted.

Changes

Any alteration of a Xtreme Msg (MMX) configuration item, or recent software installation can be the cause of this issue.

Changes in the network can also be a probable cause of this problem.

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