[ 
https://issues.apache.org/jira/browse/DIRSERVER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507335#comment-16507335
 ] 

Roland Szabó commented on DIRSERVER-2235:
-----------------------------------------

The rename operation I tried:

{{      Dn old = new Dn( oldName );}}
{{      Dn dn = old.getParent().add( new Rdn( newName ) );}}
{{      ctx.moveAndRename( old, dn, true );}}
{{      this.name = dn.getName();}}

I also tried before the simple rename:

{{      ctx.rename( oldName, newName, true );}}

The value of the String 'oldName' is the DN of the entry 
("cn=Teszt,ou=kulsos,ou=people,dc=leier"), the value of the String 'newName' is 
the new name: "cn=Teszt 2".

Both methods resulted in the same behaviour.

 

> After renaming an entry in ApacheDS, the directory loses the new entry
> ----------------------------------------------------------------------
>
>                 Key: DIRSERVER-2235
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-2235
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M20, 2.0.0-M24
>         Environment: Debian Linux, x64
>            Reporter: Roland Szabó
>            Priority: Major
>         Attachments: tesztelek.ldif
>
>
> When I rename an entry in our directory, the old entry is still returned in 
> searches but it cannot be read. The new entry exists, but only when referred 
> directly by its DN. I have to restart the server to clean this mess up.
> I tried to use the rename operation in JNDI, then I switched to the ApacheDS 
> LDAP-API, but both method results in the same problem. We use the CN 
> attribute as the RDN, and after renaming, the CN attribute of the entry is 
> all lowercase, however the DN maintains the correct casing. If I update the 
> CN attribute to the correct case, I can use the rename operation on the entry 
> 1 more time. If I also close the connection between rename operations, I can 
> rename the same entry 1 more time, but then it fails again.
> I tried to upgrade from M20 to M24, but the problem is still there.
> I do not really understand the reason...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to