You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/01/22 03:47:29 UTC
[jira] Resolved: (DIRSERVER-818) Nested delete fails when
replication enabled
[ https://issues.apache.org/jira/browse/DIRSERVER-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trustin Lee resolved DIRSERVER-818.
-----------------------------------
Resolution: Fixed
Assignee: Trustin Lee
Thanks for the patch. It's in the trunk now.
> Nested delete fails when replication enabled
> --------------------------------------------
>
> Key: DIRSERVER-818
> URL: https://issues.apache.org/jira/browse/DIRSERVER-818
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Affects Versions: pre-1.0
> Environment: Windows 2003
> Reporter: Simon Temple
> Assigned To: Trustin Lee
> Attachments: listfix-simont.patch
>
>
> I found that if a directory entry had child entries that had previously been removed and marked as deleted by the replication inteceptor, then it could not be deleted:
> From JXplorer: "Javax.naming.ContextNotEmptyException: [LDAP: error code 66 - failed to delete entry]"
>
> This is because the nextInteceptor.list() method does not return an attribute array (I guess for optimisation?) and therfore the DELETED_ENTRIES_FILTER never filtered the 'marked as deleted' entries... hence the ContextNotEmptyException.
>
> Proposed patch attached.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira