SLEE Reporting "No available call instances" or "SleeException: No more calls" or "SleeException: No more events" (Doc ID 1204644.1)

Last updated on OCTOBER 25, 2024

Applies to:

Symptoms

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:

 

Cause

Sign In	To view full details, sign in with your My Oracle Support account.
Register	Don't have a My Oracle Support account? Click to get started!

---

In this Document

Symptoms

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

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

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

Changes

Cause

Cause 1 - The most common cause for this problem is the events size is not properly defined for the SLEE

Cause 2 - Known BUG on Messaging Manager software v4.0.3.2 (or older version).

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

Solution

Solution 1 - To correct the issue, review the number of events allocated to the SLEE, and consider increasing

Solution 2 - Known BUG on Messaging Manager

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

References

---

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.