LDAP sync fails with a LDAP response read timed out error seen in the appserver.log

LDAP sync fails in Filr when syncing against some large LDAP directories with the following error stack in appserver.log file:

2017-05-09 13:47:16,605 ERROR [http-apr-8443-exec-49] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - syncUsers() threw an exception:
javax.naming.NamingException: LDAP response read timed out, timeout used:60000ms.; remaining name 'o=XYZ'
    at com.sun.jndi.ldap.Connection.readReply(Connection.java:516)
    at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:651)
    at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:574)
    at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1999)
    at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1861)
    at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1786)

LDAP timeout needs to be increased:

1. Edit the following file on the Filr application server in a text editor
/opt/novell/filr/apache-tomcat/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties

2. At the end of the file, add the following line:

com.sun.jndi.ldap.read.timeout=3000000

3. Save the file and exit.

4. A restart to Filr will be required for change to take effect.

5. The error should now be resolved.

If there are multiple Filr application servers in a cluster environment, then this setting will have to be added to each of them.