Hi Francesco; I think that you are using LDAP async source service. If so this is a bug : LSC should check and renew the connection if it has been close. Can you open an issue ?
Regards, Sebastien BAHLOUL IAM / Security specialist Ldap Synchronization Connector : http://lsc-project.org Blog : http://sbahloul.wordpress.com/ 2014-08-07 8:58 GMT+02:00 Francesco Malvezzi <francesco.malve...@unimore.it> : > Hi all, > > during async task, after a while, lsc begins logging: > > [...] > ago 07 08:45:02 - ERROR - LDAP error while reading entry > uid=a_user,ou=people,dc=example,dc=org > (org.apache.directory.ldap.client.api.exception.InvalidConnectionException: > Cannot connect on the server, the connection is invalid) > ago 07 08:45:02 - ERROR - Synchronization aborted because no source > object has been found ! > > as far as I understand, this could be connected with the following line > on the OpenLDAP ldap.log: > > [...] > Aug 7 08:43:49 b1 slapd[2666]: conn=3910631 fd=43 closed (idletimeout) > > (conn=3910631 is a connection from lsc; OpenLDAP is the source directory). > > Am I right to suppose idletimeout stops lsc during async tasks? > Shouldn't that be handled by connection pools? Aren't connection pools > enabled by default? > > Has ldapConnection>factory something to do with this issue? > > thank you, > > Francesco > > > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-users mailing list > lsc-users@lists.lsc-project.org > http://lists.lsc-project.org/listinfo/lsc-users >
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list lsc-users@lists.lsc-project.org http://lists.lsc-project.org/listinfo/lsc-users
