SLEE Applications Fail to Start with Error "SleeException: Cannot map shared memory (X) in sleeShmManager.cc at Y by process id Z errno(22) - Invalid argument"
(Doc ID 1455978.1)
Last updated on MARCH 24, 2020
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), the Service Logic Execution Environment (SLEE) is a pre-allocated chunk of Shared Memory (SHM) used by SLEE applications on the Service Logic Controllers (SLCs) and Voucher Wallet Servers (VWS') for interprocess communication.
As the allocated memory chunk used for the SLEE must be mapped into each SLEE application, if it is configured to be too large (SLEE configuration is done is /IN/service_packages/SLEE/etc/SLEE.cfg), then the SLEE application(s) will fail to start and sleeStartup will throw an error similar to the following to the SLEE log (/IN/service_packages/SLEE/tmp/SLEE.log):
Feb 10 15:15:56.713293 sleeStartup(50628) CRITICAL: Exception occured in SLEE startup, please check your configuration and try again: SleeException: Cannot map shared memory (3002) in sleeShmManager.cc at 177 by process id 50628 errno(22) - Invalid argument
This error can be caused by any of the following:
- Reconfiguration of the SLEE parameters
- Installation of new libraries
- Migration of SLEE configuration between Linux and Solaris
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