You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2006/11/06 21:26:36 UTC
[jira] Created: (DIRSERVER-774) One an entry is deleted or marked
as deleted another entry with the same DN cannot be added.
One an entry is deleted or marked as deleted another entry with the same DN cannot be added.
--------------------------------------------------------------------------------------------
Key: DIRSERVER-774
URL: http://issues.apache.org/jira/browse/DIRSERVER-774
Project: Directory ApacheDS
Issue Type: Bug
Components: mitosis
Reporter: Alex Karasulu
Priority: Blocker
Fix For: 1.5.0
There might not be any way to handle this specific issue. Might be an oversight in the design. However a solution is simple I think. We just need to really delete the entry marked for deletion and add the new entry with the same dn in it's place.
Here's the error I get from the server when trying to add the entry after having deleted it:
Root error: [LDAP: error code 68 - failed to add entry ou=neworganizationalUnit,dc=example,dc=com: 2.5.4.11=neworganizationalunit,0.9.2342.19200300.100.1.25=example,0.9.2342.19200300.100.1.25=com already exists.]
which means ...
LDAP_ALREADY_EXISTS: Indicates that the add operation attempted to add an entry that already exists, or that the modify operation attempted to rename an entry to the name of an entry that already exists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DIRSERVER-774) One an entry is deleted or marked
as deleted another entry with the same DN cannot be added.
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-774?page=all ]
Alex Karasulu reassigned DIRSERVER-774:
---------------------------------------
Assignee: Alex Karasulu
> One an entry is deleted or marked as deleted another entry with the same DN cannot be added.
> --------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-774
> URL: http://issues.apache.org/jira/browse/DIRSERVER-774
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Reporter: Alex Karasulu
> Assigned To: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.0
>
>
> There might not be any way to handle this specific issue. Might be an oversight in the design. However a solution is simple I think. We just need to really delete the entry marked for deletion and add the new entry with the same dn in it's place.
> Here's the error I get from the server when trying to add the entry after having deleted it:
> Root error: [LDAP: error code 68 - failed to add entry ou=neworganizationalUnit,dc=example,dc=com: 2.5.4.11=neworganizationalunit,0.9.2342.19200300.100.1.25=example,0.9.2342.19200300.100.1.25=com already exists.]
>
> which means ...
> LDAP_ALREADY_EXISTS: Indicates that the add operation attempted to add an entry that already exists, or that the modify operation attempted to rename an entry to the name of an entry that already exists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DIRSERVER-774) One an entry is deleted or marked as
deleted another entry with the same DN cannot be added.
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-774?page=all ]
Alex Karasulu closed DIRSERVER-774.
-----------------------------------
Resolution: Fixed
Ok I fixed the issue with sitations where the marked for delete entry actually has children marked as deleted using a recursive delete.
I also fixed a bug with list() operations showing deleted entries because they do not pull out the entryDeleted attribute for filtering to occur.
http://svn.apache.org/viewvc?view=rev&revision=472175
> One an entry is deleted or marked as deleted another entry with the same DN cannot be added.
> --------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-774
> URL: http://issues.apache.org/jira/browse/DIRSERVER-774
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: mitosis
> Reporter: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.0
>
>
> There might not be any way to handle this specific issue. Might be an oversight in the design. However a solution is simple I think. We just need to really delete the entry marked for deletion and add the new entry with the same dn in it's place.
> Here's the error I get from the server when trying to add the entry after having deleted it:
> Root error: [LDAP: error code 68 - failed to add entry ou=neworganizationalUnit,dc=example,dc=com: 2.5.4.11=neworganizationalunit,0.9.2342.19200300.100.1.25=example,0.9.2342.19200300.100.1.25=com already exists.]
>
> which means ...
> LDAP_ALREADY_EXISTS: Indicates that the add operation attempted to add an entry that already exists, or that the modify operation attempted to rename an entry to the name of an entry that already exists.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira