2013/11/4 Maxime Pelletier <[email protected]> > Clément OUDOT <[email protected]> a écrit : > > > > > 2013/11/4 Maxime Pelletier <[email protected]> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> *Hi all, Any idea how to fix that error while syncing with OpenLDAP: >> ===================== Nov 04 09:26:20 - INFO - Starting clean for Eleves >> Nov 04 09:30:35 - ERROR - Error while deleting entry >> uid=XXXXXX,ou=Personne,dc=myorg directory >> :javax.naming.CommunicationException: connection closed [Root exception is >> java.io.IOException: connection closed]; remaining name >> 'uid=XXXXXXX,ou=Personne' Nov 04 09:30:35 - ERROR - Error while >> synchronizing ID uid=XXXXXX,ou=Personne,dc=myorg: >> org.lsc.exception.LscServiceException: javax.naming.CommunicationException: >> connection closed [Root exception is java.io.IOException: connection >> closed]; remaining name 'uid=XXXXXXXX,ou=Personne' dn: >> uid=XXXXXX,ou=Personne,dc=myorg changetype: delete Nov 04 09:30:35 - ERROR >> - Connection lost! Aborting. ===================== Looks like some OpenLDAP >> timeout setting is too short and that it disconnects LSC before the >> exexution is complete. Based on Google research,I tried these settings in >> JAVA_OPTS but no luck: -Djava.naming.ldap.version=2 >> -Dcom.sun.jndi.ldap.read.timeout=60000 >> -Dcom.sun.jndi.ldap.connect.pool=false >> -Dcom.sun.jndi.ldap.connect.timeout=60000 Any idea?* >> > > > > > *Seems not a good idea to use LDAPv2. We do not have such timeout > problems, do you know why the connection is closed? Clément.* > > Hi Clément, > > LDAPv2 didn't work... > > I think that our OpenLDAP server automatically close the connection after > 4 minutes. > >
Have you any timeout configured in OpenLDAP? > During the clean phase, my understanding is that LSC is constantly > querying LDAP so it shouldn't get any kind of timeout. > No it is not. During clean phase, a search is done on the destination, to get all entries. After this first search, a search is done in source for each entry using the pivot attribute. The entry is deleted in destination if not found in source. So if there is a lot of entries, you can have a timeout in destination before calling the first delete. > By default, is LSC using pooling? Not sure if this can have an impact. > > I think not. Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
