Connection Timed Out Error On AD Non Ssl Port

(Doc ID 2171695.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Access Manager - Version to [Release 11g]
Information in this document applies to any platform.
Environment Details
OHS : (2 nodes)

OID : (2 nodes) -- WebLogic 10.3.6 PSU 13

OIM : BP 04 (2 nodes) -- WebLogic 10.3.6 PSU 13

OAM : BP 04 (2 nodes) -- WebLogic 10.3.6 PSU 12

DB : Oracle database (2 node RAC)

weblogic version:


Connection timed out with AD with non ssl port and below are error details.

[2016-08-09T11:25:47.610+05:30] [oam_server1] [WARNING] [LIBOVD-60176] [oracle.ods.virtualization.exception] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuni ng)'] [userId: <anonymous>] [ecid: a3fcb323e32e4de0:6cabf0c2:1563423f50a:-8000-000000000014aa81,0:4:1] [APP: oam_server#] JNDI exception: {0}.[[
javax.naming.CommunicationException: [Root exception is connect timed out]
at com.sun.jndi.ldap.Connection.<init>(
at com.sun.jndi.ldap.LdapClient.<init>(
at com.sun.jndi.ldap.LdapClient.getInstance(
at com.sun.jndi.ldap.LdapCtx.connect(
at com.sun.jndi.ldap.LdapCtx.<init>(
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(


 - when authentication a user through OAM SSO login page it will check the user in our Directory services which is chained ldap(AD+OID) on our end.
user will be searched in a AD first if not found then it will check in OID.

- while authentication for AD user we are getting connection time out error on 389 Port which is non ssl.


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