My Oracle Support Banner

OUD & Oracle Business Process Management (BPM) REST API - Frequent Errors in BPM Diagnostic Logs "LDAP connection has been closed" (Doc ID 2953959.1)

Last updated on JUNE 12, 2023

Applies to:

Oracle Unified Directory - Version 12.2.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.4.0 version, OUD Core

Oracle Business Process Management (BPM) using OUD as a backend LDAP through a loadbalancer.

Frequently "LDAP connection has been closed errors" are being reported in the BPM diagnostic logs.

<Jun 3, 2023 1:05:21,540 PM AST> <Warning> <oracle.ods.virtualization.engine.backend.jndi.OUDAuthenticator> <LIBOVD-40066> <Remote Server Failure:<OUD_LBR_HOSTNAME:LBR PORT>javax.naming.NamingException: LDAP connection has been closed; remaining name 'dc=<SUFFIX>'
at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:133)
at com.sun.jndi.ldap.Connection.readReply(Connection.java:479)
at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:638)
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:561)
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2014)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1873)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1798)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:392)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:358)
at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:276)
at oracle.ods.virtualization.engine.backend.jndi.ConnectionHandle.search(ConnectionHandle.java:338)
at oracle.ods.virtualization.engine.backend.jndi.JNDIEntrySet.initialize(JNDIEntrySet.java:228)
at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.get(BackendJNDI.java:833)
at oracle.ods.virtualization.engine.chain.Chain.nextGet(Chain.java:303)

It's also been seen in lower environments to a much lesser extent. The LDAP backend used is OUD. "libOVD" is in the middle of attempting to use the connection from the application (BPM) and when it tries to perform the ldapsearch it finds the connection is closed.

Also observed is that ldapsearch via OUD through the loadbalancer is taking 4 to 8 minutes, whereas to OUD directly it is less than a second. Need to determine why the connections are being closed.

 

 

Cause

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
Symptoms
Cause
Solution
References


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