MTUTILS PATCH FAILS WITH OID CONNECTION CLOSED "javax.naming.CommunicationException: connection closed" (Doc ID 2046047.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Oracle Access Manager - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Symptoms

During execution of 15.1.6 MTutils patch for OAM, failures occur with OID.



Example from Log:
Jun 14, 2015 3:37:11 AM oracle.jldif.util.LDIFLoader loadRecord
SEVERE: Unable to establish connection to directory. Verify the input
@ parameters: host, port, dn & passwordconnection closed
Exception found
oracle.idm.multitenancy.exception.IDMMultiTenancyException
at oracle.idm.multitenancy.util.Util.getTenantGuid(Util.java:1017)
at
oracle.idm.multitenancy.impl.enablemt.LDAPEnableMultiTenancy.createDatacenterA
ppIDs(LDAPEnableMultiTenancy.java:1070)
at
oracle.idm.multitenancy.impl.enablemt.LDAPEnableMultiTenancy.enableMT(LDAPEnab
leMultiTenancy.java:231)
at
oracle.idm.multitenancy.OrclTenantManager.enableMT(OrclTenantManager.java:881)

at oracle.idm.multitenancy.OrclTenantManager.main(OrclTenantManager.java:256)
Caused by: javax.naming.CommunicationException: connection closed [Root
exception is java.io.IOException: connection closed]; remaining name
'dc=cloud,dc=oracle,dc=com'
@ at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1983)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1827)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1752)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java
:368)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDir
Context.java:338)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDir
Context.java:321)
at
javax.naming.directory.InitialDirContext.search(InitialDirContext.java:248)
at oracle.idm.multitenancy.util.Util.getTenantGuid(Util.java:1001)
... 4 more
Caused by: java.io.IOException: connection closed
at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java:1567)

 

 

When running enbleMT, one OID thread is getting killed and a new
thread is spawned and Core is getting generated.

Cause

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