slee_acs Process Crashes after Logging: "CRITICAL SleeException=34 sleeError.cc@53: SleeException: Semaphore operation failed (1005) in sleeUnixSemaphore.cc at 138 by process id <PID> errno(34) - Result too large" (Doc ID 2007038.1)

Last updated on JULY 18, 2016

Applies to:

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

Symptoms

In all versions of Oracle Network Charging and Control (NCC) running on Solaris 10 and 11, a problem can present itself on the Service Logic Controllers when they are experiencing load.

The slee_acs processes can log the following error then be killed by the watchdog, leaving behind a core file:

CRITICAL SleeException=34 sleeError.cc@53: SleeException: Semaphore operation failed (1005) in sleeUnixSemaphore.cc at 138 by process id 16112 errno(34) - Result too large

 

Changes

Higher load than usual and/or lower performance capabilities of the hardware running the affected Sevice Logic Execution Environment (SLEE).

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