Environment
Novell Filr 2.0
Situation
On some Filr systems LDAP sync task fails when there is sufficient idle time (in some tests 25 minutes) between the last time Filr contacted the LDAP server. This can happen if processing of users/groups takes long enough before the next set of users/groups is requested from the LDAP server.
The following error stack sequence is observed in appserver.log file when this happens:
2016-02-02 16:24:30,746 ERROR [http-apr-8443-exec-12] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - An error was encountered syncing groups. Ldap sync will not continue.
2016-02-02 16:24:30,746 ERROR [http-apr-8443-exec-12] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - Exception encountered while syncing groups:
org.kablink.teaming.domain.LdapSyncException: Connection reset
...
...
Caused by: javax.naming.CommunicationException: Connection reset [Root exception is java.net.SocketException: Connection reset]; remaining name 'ou=Departments,dc=hr,dc=abc,dc=uk'
...
...
Caused by: java.net.SocketException: Connection reset
The following error stack sequence is observed in appserver.log file when this happens:
2016-02-02 16:24:30,746 ERROR [http-apr-8443-exec-12] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - An error was encountered syncing groups. Ldap sync will not continue.
2016-02-02 16:24:30,746 ERROR [http-apr-8443-exec-12] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - Exception encountered while syncing groups:
org.kablink.teaming.domain.LdapSyncException: Connection reset
...
...
Caused by: javax.naming.CommunicationException: Connection reset [Root exception is java.net.SocketException: Connection reset]; remaining name 'ou=Departments,dc=hr,dc=abc,dc=uk'
...
...
Caused by: java.net.SocketException: Connection reset
Resolution
A fix for this issue is available in the Filr 2.0 Hot Patch 1, available via the Novell Patch Finder.