You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2009/08/19 13:14:14 UTC
[jira] Updated: (DIRSERVER-1401) Infinite loop on moddn, when
moving an entry below itself
[ https://issues.apache.org/jira/browse/DIRSERVER-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1401:
-----------------------------------------
Fix Version/s: 2.0.0-RC1
Definitively to fix ASAP
> Infinite loop on moddn, when moving an entry below itself
> ---------------------------------------------------------
>
> Key: DIRSERVER-1401
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1401
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 1.5.5, 1.5.4
> Reporter: Stefan Seelmann
> Priority: Critical
> Fix For: 2.0.0-RC1
>
>
> Running the following LDIF causes an infinite loop (100% CPU of the ApacheDS process), the client waits for response. The two entries are created, the moddn operation then hangs.
> -------------------------------------------------------------------------------
> # create parent entry
> dn: ou=parent,dc=example,dc=com
> changetype: add
> objectClass: organizationalUnit
> objectClass: top
> ou: parent
> # create child entry
> dn: ou=child,ou=parent,dc=example,dc=com
> changetype: add
> objectClass: organizationalUnit
> objectClass: top
> ou: child
> # now do something bad: make the parent a child of its own child
> dn: ou=parent,dc=example,dc=com
> changetype: moddn
> newrdn: ou=parent
> deleteoldrdn: 1
> newsuperior: ou=child,ou=parent,dc=example,dc=com
> -------------------------------------------------------------------------------
> I'd expect an error, OpenLDAP for example returns "error code 53 - cannot place an entry below itself"
> Another problem: When I kill the server and start it again, the two inserted entries are not visible studio, but when trying to add them I get an "error code 68 - ENTRY_ALREADY_EXISTS". Seems loke the indices got corrupted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.