SLEE Applications Unable to (Re-)Attach to SLEE After SLEE has been Up for Over 11 Days (Doc ID 2255959.1)

Last updated on APRIL 19, 2017

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Linux x86-64

Symptoms

On all versions of Oracle Communications Convergent Charging Controller (OC3C) on Oracle Linux platforms, a problem exists where the Service Logic Execution Environment (SLEE) temporary file is being deleted after the SLEE has been up for 11 continuous days.

As a result, any attempt to connect to the running SLEE will fail with the following error:

Apr 11 17:21:57 check(24216) SleeException=2 sleeError.cc@50: SleeException: Temp file not found (1) in sleeShmManager.cc at 109 by process id 24216 errno(2) - No such file or directory
Temp file not found
check: error: could not connect to SLEE

This affects any dead SLEE application which the watchdog tries to restart and any ad-hoc SLEE process such as check or slpit.

Changes

The SLEE was (re-)started and has been up for over 11 days.

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