SLEE Reporting "No available call instances" or "SleeException: No more calls" or "SleeException: No more events"

(Doc ID 1204644.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

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

Symptoms

This article aims to explain about some possible causes that can lead Service Logic Execution Environment (SLEE) reporting about:
- "No available call instances"
- or "SleeException: No more calls"
- or "SleeException: No more events".
However, those causes may not be related with each others. Instead, those causes are documented to make identification easier.

 

1. SLEE running out of events to handle incoming requests via a SLEE interface or requests generated by a SLEE application, such as slee_acs sending a profile update request or update statistics

 

Example error messages found in the /var/adm/messages would include:
Jul 28 04:33:02 <process>(21324) SleeCallInstance::new()=11 sleeCallInstance.cc@94: No available call instances
Jul 28 04:33:02 <process>(21324) SleeException=8006 sleeError.cc@59: SleeException: No more calls (8006) in sleeCallInstance.cc at 99 by process id 21324
Jul 28 04:33:02 <process>(21324) SleeInterfaceAPI=8006 sleeInterfaceAPI.cc@248: Overload: SLEE is out of call instances
Jul 28 04:33:02 <process>(21324) SleeCallInstance::new()=11 sleeCallInstance.cc@94: No available call instances
Jul 28 04:33:02 <process>(21324) SleeException=8006 sleeError.cc@59: SleeException: No more calls (8006) in sleeCallInstance.cc at 99 by process id 21324
Jul 28 04:33:02 <process>(21324) SleeInterfaceAPI=8006 sleeInterfaceAPI.cc@248: Overload: SLEE is out of call instances

 

Note that <process> could be slee_acs, or the Network Control Agent (NCA) interface process (e.g. diameterControlAgent, cdmaGateway, xmsTrigger, VWAR, etc)

 

VWAR:Processing Exception: VWARS: Could not send VWARS response: SleeException: No more events (8002) in sleeEvent.cc at 70 by process id 22242
CCSCD1=QRY:NACK:69-Error querying BE for msisdn xxxxxxxxxxx: VWAR:Processing Exception: VWARS: Could not send VWARS response: SleeException: No more events (8002) in sleeEvent.cc at 70 by process id 22242,SYNSTAMP=2010122810004439;
For detailed information about how to determine the SLEE is leaking please refer to doc id 1289659.1
You can refer to "The most common cause for this problem is not having enough oversized events defined for the SLEE" for further explanation about the cause.

2. Though the SLEE resource utilization is increasing, the Call Attempt Per Second (CAPS) rate shows normal condition (no traffic spike)

Please compare the SLEE resource utilization against traffic rate, if traffic rate looks normal without spike indication but the SLEE resource is keep increasing then this situation can be considered as leaking issue.

For detailed information about how to determine the SLEE is leaking please refer to doc id 1289659.1




The illustration for SLEE resource v.s Traffic rate is seen by this following graph:


Graph 1. SLEE resource utilization


Graph 2. Traffic rate (CAPS rate)
Those two graphs show on the same period of time, the SLEE resource utilization is keep increasing till reach the top, although the traffic rate is steady/normal.

You can refer to "Known BUG on Messaging Manager software" for further explanation about one of possible cause.

3.Call Initiation (CI) Node Causes Event Leak After Receiving Empty TCAP-END

         USSD Call Back Call Flow (A-Party no answer) :




The symptom for this issue can be summarized as follows:
  • During USSD Callback call setup, the SLC drops the call when the Mobile Switching Center (G/MSC) has connected the call to the A party and is waiting for Answer (ISUP ANM message). In other words the SLC drops the call when the A party's phone is ringing (Call is disconnected before NoAnswer timeout)
  • Timeout displayed in USSD log:
    Oct 29 10:04:46 ussd(3632) CRITICAL: USSD: Direct Trigger Timed Out
  • SLEE resource is leaking
Please review symptom 1 & 2 to check and verify the SLEE resource

Changes

  1. Gradual increase in traffic on the platform could cause this to happen
  2. New services, based on periodic charge mechanism using balance types, have been assigned to the end users. (Note: only applicable if the error occurred on VWS related process)
  3. Installing new software component (either patch or interim patch) which could be having a bug.

 

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