LDAP Error 1 After Enabling libOVD: oracle.ods.virtualization.engine.util.DirectoryException: LDAP Error 1 : [LDAP: error code 1 - LDAP Error 1 : Error Communicating with database: IO Error: The Network Adapter could not establish the connection-08006]
(Doc ID 2399491.1)
Last updated on AUGUST 17, 2022
Applies to:
Oracle Virtual Directory - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
Environment with Business Process Management (BPM) and Oracle Virtual Directory (OVD) as the authenticator.
After enabling libOVD, Weblogic Server (WLS) logs start to show:
[LDAP: error code 1 - LDAP Error 1 : Error Communicating with database: IO Error: The Network Adapter could not establish the connection-08006]
Application diagnostic log also shows:
[2018-03-02T21:31:06.959+03:00] [xxxxx] [TRACE] [LIBOVD-20131] [oracle.ods.virtualization] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <USER>] [ecid: <ECID>] [APP: xxxx] [SRC_CLASS: oracle.ods.virtualization.engine.util.VDELogger] [SRC_METHOD: debug] Returning NEW stream: /<OVD_IP_ADDRESS>:<PORT> ThreadGroup: [ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'.
[2018-03-02T21:31:06.991+03:00] [xxxx] [WARNING] [LIBOVD-40066] [oracle.ods.virtualization.engine.backend.jndi.BPMAuth] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <USER>] [ecid: <ECID>] [APP: xxxx] Remote Server Failure:<OVD_IP_ADDRESS>:<PORT>.[[ javax.naming.NamingException:
[LDAP: error code 1 - LDAP Error 1 : Error Communicating with database: IO Error: The Network Adapter could not establish the connection-08006]; remaining name 'dc=<COMPANY>,dc=com'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3129)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3035)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2841)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1850)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1773)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:386)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:356)
at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:276)
at oracle.ods.virtualization.engine.backend.jndi.ConnectionHandle.search(ConnectionHandle.java:262)
at oracle.ods.virtualization.engine.backend.jndi.JNDIEntrySet.initialize(JNDIEntrySet.java:221)
at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.get(BackendJNDI.java:732)
at oracle.ods.virtualization.engine.chain.Chain.nextGet(Chain.java:303)
........
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 |