Another thing that I've noticed is that once this exception happens
and I change something in the AD,
I get this error:
Feb 18 07:38:15 - ERROR - LDAP error while reading entry CN=Some
User,OU=Users,OU=ad-testing,DC=ad-testing,DC=test,DC=io
(org.apache.directory.ldap.client.api.exception.InvalidConnectionException:
Cannot connect on the server, the connection is invalid)
Feb 18 07:38:15 - DEBUG -
org.apache.directory.ldap.client.api.exception.InvalidConnectionException:
Cannot connect on the server, the connection is invalid
org.apache.directory.ldap.client.api.exception.InvalidConnectionException:
Cannot connect on the server, the connection is invalid
at
org.apache.directory.ldap.client.api.LdapNetworkConnection.checkSession(LdapNetworkConnection.java:271)
~[api-all-1.0.0-M22.jar:1.0.0-M22]
at
org.apache.directory.ldap.client.api.LdapNetworkConnection.searchAsync(LdapNetworkConnection.java:1667)
~[api-all-1.0.0-M22.jar:1.0.0-M22]
at
org.apache.directory.ldap.client.api.LdapNetworkConnection.search(LdapNetworkConnection.java:1710)
~[api-all-1.0.0-M22.jar:1.0.0-M22]
at
org.apache.directory.ldap.client.api.LdapNetworkConnection.search(LdapNetworkConnection.java:1603)
~[api-all-1.0.0-M22.jar:1.0.0-M22]
at
org.apache.directory.ldap.client.api.LdapNetworkConnection.search(LdapNetworkConnection.java:1613)
~[api-all-1.0.0-M22.jar:1.0.0-M22]
at
org.lsc.service.SyncReplSourceService.getBean(SyncReplSourceService.java:250)
~[lsc-core-2.1.4.jar:na]
at org.lsc.SynchronizeTask.run(AbstractSynchronize.java:689)
[lsc-core-2.1.4.jar:na]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[na:1.8.0_151]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[na:1.8.0_151]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_151]
On Tue, Feb 13, 2018 at 5:04 PM, Lior Dotan <[email protected]> wrote:
> Hi,
>
> I am syncing data from Active Directory and it's working fine in sync
> mode but when running in async mode I see the following error in the
> log and the data is no longer being synced.
>
> Feb 13 14:18:46 ip-10-0-135-60 sync[12163]: Feb 13 14:18:46 - DEBUG -
> Asynchronous synchronize SyncUserTask
> Feb 13 14:33:55 ip-10-0-135-60 sync[12163]: Feb 13 14:33:55 - WARN -
> Connection reset by peer
>
> Is the 15 minutes timeout can be configured on the LSC or AD side?
> Is there some way to establish the connection again without restarting LSC?
>
> Thanks,
> Lior
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
