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 NOVEMBER 08, 2018
Applies to:Oracle Communications Network Charging and Control - Version: 2.2.0
Information in this document applies to any platform.
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 in the network can also be a probable cause of this problem.
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
Permanent solution (available for Xtreme Msg version 3.1+)
Workaround solution (available for all Xtreme Msg version under 3.1)