ERROR: [DM_LDAP_SYNC_E_LDAP_NAMING_EXCEPTION]

rishigiram
rishigiram Member
edited May 28, 2013 in Documentum #1

We are getting following error after running the LDAP job

2013-05-22 04:03:22 EDT:  ERROR: [DM_LDAP_SYNC_E_LDAP_NAMING_EXCEPTION]: Explanation:null: RemainingName:null: ResolvedName:null: ResolvedObj:null: Exception Class:class javax.naming.PartialResultException: Message:null: Cause:javax.naming.CommunicationException: abc.com:389 [Root exception is java.net.SocketException: Connection timed out:could be due to invalid address]: Exception Detail:javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: abc.com:389 [Root exception is java.net.SocketException: Connection timed out:could be due to invalid address]]: Stack Trace

javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: abc.com:389 [Root exception is java.net.SocketException: Connection timed out:could be due to invalid address]]

    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:239)

    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreReferrals(LdapNamingEnumeration.java:377)

    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:223)

    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore(LdapNamingEnumeration.java:186)

    at com.documentum.ldap.internal.ldap.jndi.PagedJndiEntryIterator.hasNext(PagedJndiEntryIterator.java:46)

    at com.documentum.ldap.internal.processors.DirectoryProcessor.hasNext(DirectoryProcessor.java:127)

    at com.documentum.ldap.internal.sync.SynchronizeUser.startSynchronization(SynchronizeUser.java:48)

    at com.documentum.ldap.LDAPSync.processSync(LDAPSync.java:355)

    at com.documentum.ldap.LDAPSync.processJob(LDAPSync.java:157)

    at com.documentum.ldap.LDAPSync.execute(LDAPSync.java:66)

    at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)

    at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)

    at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)

    at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)

    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)

    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)

    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)

    at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)

    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)

    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)

    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

    at java.lang.Thread.run(Thread.java:801)

Caused by: javax.naming.CommunicationException: cotyww.com:389 [Root exception is java.net.SocketException: Connection timed out:could be due to invalid address]

    at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapReferralContext.java:99)

    at com.sun.jndi.ldap.LdapReferralException.getReferralContext(LdapReferralException.java:147)

    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreReferrals(LdapNamingEnumeration.java:354)

    at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl(LdapNamingEnumeration.java:223)

    ... 33 more

Caused by: java.net.SocketException: Connection timed out:could be due to invalid address

    at java.net.PlainSocketImpl.socketConnect(Native Method)

    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:372)

    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:233)

    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:220)

    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385)

    at java.net.Socket.connect(Socket.java:541)

    at java.net.Socket.connect(Socket.java:491)

    at java.net.Socket.<init>(Socket.java:399)

    at java.net.Socket.<init>(Socket.java:208)

    at com.sun.jndi.ldap.Connection.createSocket(Connection.java:374)

    at com.sun.jndi.ldap.Connection.<init>(Connection.java:209)

    at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:133)

    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1593)

    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2611)

    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:298)

    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:190)

    at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:149)

    at com.sun.jndi.url.ldap.ldapURLContextFactory.getObjectInstance(ldapURLContextFactory.java:50)

    at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:596)

    at javax.naming.spi.NamingManager.processURL(NamingManager.java:376)

    at javax.naming.spi.NamingManager.processURLAddrs(NamingManager.java:356)

    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:328)

    at com.sun.jndi.ldap.LdapReferralContext.<init>(LdapReferralContext.java:118)

    ... 36 more

We are using CS 6.5SP1 and DA 6.7...

Tagged:

Comments

Categories