High CPU Usage by ldapIF
(Doc ID 2372677.1)
Last updated on JULY 20, 2018
Applies to:Oracle Communications Network Charging and Control - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 12.0.0]
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) release 220.127.116.11, the Data Access Pack (DAP) module now has the ability to look up Lightweight Directory Access Protocol (LDAP) services.
In order to achieve this, a new process, ldapIF, was built which is called by the DAP Request Feature Node (FN) when a request is to be sent over the LDAP protocol (please see the DAP User and Technical Guide for more information).
When the ldapIF process starts as part of the Service Logic Execution Environment (SLEE), it hogs 100% of a CPU even when it is not handling any requests.
Installation of NCC or 3C 18.104.22.168.
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