Issue #543 has been updated by Clément OUDOT. Status changed from Assigned to Closed % Done changed from 50 to 100
Tested today with my updated distribution, and I don't have the problem anymore: <pre> clement@ader-xps:~$ Programmes/lsc-2.1-SNAPSHOT/bin/lsc -f configuration/lsc/linid/openldap2ad/ -c user -t1 mai 13 16:43:53 - INFO - Logging configuration successfully loaded from /home/clement/configuration/lsc/linid/openldap2ad/logback.xml mai 13 16:43:53 - INFO - LSC configuration successfully loaded from /home/clement/configuration/lsc/linid/openldap2ad/ mai 13 16:43:54 - INFO - Connecting to LDAP server ldaps://ad.example.com/DC=example,DC=com as cn=demo,cn=Users,dc=example,dc=com mai 13 16:43:54 - INFO - Connecting to LDAP server ldap://localhost/dc=example,dc=com as cn=admin,dc=example,dc=com mai 13 16:43:54 - INFO - Starting clean for user mai 13 16:43:54 - DEBUG - Using pagedResults control for 1000 entries at a time mai 13 16:43:54 - INFO - # Removing object CN=test,OU=users,OU=demo,DC=example,DC=com for user # Tue May 13 16:43:54 CEST 2014 dn: CN=test,OU=users,OU=demo,DC=example,DC=com changetype: delete mai 13 16:43:54 - INFO - All entries: 3, to modify entries: 1, successfully modified entries: 1, errors: 0 clement@ader-xps:~$ java -version java version "1.7.0_55" OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1) OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) </pre> ---------------------------------------- Bug #543: Clean phase with asyncLdapSourceService http://tools.lsc-project.org/issues/543 Author: Clément OUDOT Status: Closed Priority: Low Assigned to: Raphaël Ouazana Category: Core Target version: 2.1 Problem in version: Not a major issue, but may be interesting to look at it. When launching the clean phase for an asyncLdapSourceService, we have a message like this for each search on the source directory : <pre> nov. 15 10:40:02 - ERROR - There is no future associated with operation message ID 30073, perhaps the operation would have been completed </pre> And this in OpenLDAP log: <pre> Nov 15 10:37:35 qlf-mldap-v01 slapd[2594]: conn=1149076 op=2783 SRCH base="ou=people,ou=XXX" scope=2 deref=3 filter="(&(objectClass=XXX)(XXX=AAA))" Nov 15 10:37:35 qlf-mldap-v01 slapd[2594]: conn=1149076 op=2783 SRCH attr=cn sn uid displayName givenName XXX Nov 15 10:37:35 qlf-mldap-v01 slapd[2594]: conn=1149076 op=2783 SEARCH RESULT tag=101 err=0 nentries=1 text= Nov 15 10:37:35 qlf-mldap-v01 slapd[2594]: conn=1149076 op=2784 ABANDON msg=2784 </pre> What is strange, is that the ABANDON message is not done on the previous operation (2783) but on the ABANDON message itself (2784). Other remark, the clean phase do a search on source directory with all attributs configured. It seems not very usefull as we only need to know if the entry exists to delete the destination entry. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
