Issue #543 has been updated by Raphaël Ouazana.

Status changed from Assigned to Feedback
Assigned to changed from Raphaël Ouazana to Clément OUDOT
% Done changed from 0 to 50

This seems to be fixed with the new version of Apache Directory API, please 
test.
----------------------------------------
Bug #543: Clean phase with asyncLdapSourceService
http://tools.lsc-project.org/issues/543

Author: Clément OUDOT
Status: Feedback
Priority: Low
Assigned to: Clément OUDOT
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

Reply via email to