[
https://issues.apache.org/jira/browse/DIRSERVER-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623399#action_12623399
]
Kiran Ayyagari commented on DIRSERVER-1211:
-------------------------------------------
Pasting the text of IM chat with Alex regarding this issue
Alex: it's a corner case of the protocol's handling of doing a modify replace
on a non existent attribute
Kiran Ayyagari: ah ok
Alex: question is should the modify be converted to a modify add when it was
originally a modify replace when the ou attribute is not in the entry
Alex: or should it be ignored, or what's the accurate error code to return
Alex: seems indexing is affecting the behavior of this
Kiran Ayyagari: the ou index doesn't contain this id cause the first ldif entry
doesn't contain a ou attribute
Kiran Ayyagari: when I tried after giving 'ou: system' in the first entry it
was replaced properly
Alex: right
Alex: I guess deep down in jdbm store layer
Alex: the code sees there's an index on ou
Kiran Ayyagari: yep
Alex: and thinks the ou attribute must exist for the entry when replace is
being issued and tries to remove it
Kiran Ayyagari: right
Alex: this presumption causes an exception
Kiran Ayyagari: true
Alex: which circumvents normal handling
Alex: normal result response
Alex: just need to check before doing the remove on a replace operation
> Error code 54 in modify-replace operation
> -----------------------------------------
>
> Key: DIRSERVER-1211
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1211
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.3
> Reporter: Stefan Seelmann
> Assignee: Emmanuel Lecharny
>
> This error occurs with apacheds-1.5.3-fixed.tar.gz and the current
> trunk-with-dependencies (Revision 680187), both with default server.xml
> I use studio to run the following LDIF:
> ---------------------------------------------
> dn: cn=Kate Bush,ou=system
> changetype: add
> objectClass: top
> objectClass: person
> objectClass: organizationalPerson
> objectClass: inetOrgPerson
> cn: Kate Bush
> sn: Bush
> dn: cn=Kate Bush,ou=system
> changetype: modify
> replace: ou
> ou: Test
> -
> ---------------------------------------------
> The second LDIF record fails with error 54. The log is here:
> http://www.pastebin.org/57617.
> The error does not occur when I use 'add:ou' instead of 'replace:ou'
> The error does not occur when I use another attribute, e.g. 'decription'
> instead of 'ou'
> Emmanuel's idea on IM was that it is because 'ou' is indexed in the default
> server.xml.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
