LDAPReader Error - Unprocessed Continuation Reference(s)

CloverDX Platform
1

When running a graph with an LDAPReader component, a user is getting the following error message:


13:31:44,483 ERROR [WatchDog_1] Component [LDAPReader:LDAPREADER] finished with status ERROR. (Out0: 0 recs)
 javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=test,dc=cloverdx,dc=com'
13:31:44,486 ERROR [WatchDog_1] Error details:
org.jetel.exception.JetelRuntimeException: Component [LDAPReader:LDAPREADER] finished with status ERROR. (Out0: 0 recs)
	at org.jetel.graph.Node.createNodeException(Node.java:655)
	at org.jetel.graph.Node.run(Node.java:620)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=ssotest,dc=javlinlocal,dc=lll'
	at com.linagora.ldap.LdapParser.initNonPaged(LdapParser.java:299)
	at com.linagora.ldap.LdapParser.setDataSource(LdapParser.java:401)
	at com.linagora.component.LdapReader.execute(LdapReader.java:304)
	at org.jetel.graph.Node.run(Node.java:580)
	... 3 more
Caused by: javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=ssotest,dc=javlinlocal,dc=lll'
	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2914)
	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2888)
	at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.getNextBatch(AbstractLdapNamingEnumeration.java:148)
	at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMoreImpl(AbstractLdapNamingEnumeration.java:217)
	at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMore(AbstractLdapNamingEnumeration.java:189)
	at com.linagora.ldap.LdapParser.initNonPaged(LdapParser.java:280)
	... 6 more
2

The solution to the problem is the following:

  • When using the port 389 in the URL, change it to 3268.

  • When using the port 636 in the URL (when connecting via SSL), change it to 3269.

More information about why it works this way can be found either in the Microsoft Active Directory forums or on Stack Overflow.