[ http://issues.apache.org/jira/browse/DIREVE-307?page=comments#action_12357523 ]
Stefan Zoerner commented on DIREVE-307: --------------------------------------- I tried to reproduce this one, and was able to. It occurred with the client tools provided by OpenLDAP, but not with the command line tools provided by Solaris9 and IBM Tivoli Directory Server 6.0. I am still trying to understand, what the OpenLDAP client does, if blank lines are provided. Btw.: the other tools behave totally different. > ldapmodrdn failed upon encountering blank space > ----------------------------------------------- > > Key: DIREVE-307 > URL: http://issues.apache.org/jira/browse/DIREVE-307 > Project: Directory Server > Type: Bug > Components: protocol > Versions: 0.9.3 > Reporter: Endi S. Dewata > Assignee: Alex Karasulu > > When specifying multiple entries for ldapmodrdn operation, according to the > manual page (http://linuxcommand.org/man_pages/ldapmodrdn1.html) "one or more > blank lines may be used to separate each DN/RDN pair." However, it seems that > currently ApacheDS does not allow any blank lines in the ldapmodrdn input. > Note: I'm not sure if at least one blank line is actually required to > separate the entires. To be safe, the blank line maybe can be made totally > optional. > The following operation currently will succeed in renaming both entries. > > ldapmodrdn -h localhost -p 10389 -D uid=admin,ou=system -w secret -r > ou=test,dc=apache,dc=org > ou=test2 > ou=test2,dc=apache,dc=org > ou=test > The following command currently will fail on the second entry: > > ldapmodrdn -h localhost -p 10389 -D uid=admin,ou=system -w secret -r > ou=test,dc=apache,dc=org > ou=test2 > ou=test2,dc=apache,dc=org > ou=test > Here is the exception: > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.RangeCheck(ArrayList.java:507) > at java.util.ArrayList.remove(ArrayList.java:392) > at org.apache.ldap.common.name.LdapName.remove(LdapName.java:605) > at > org.apache.ldap.server.protocol.ModifyDnHandler.messageReceived(ModifyDnHandler.java:79) > at > org.apache.mina.protocol.handler.DemuxingProtocolHandler.messageReceived(DemuxingProtocolHandler.java:70) > at > org.apache.mina.protocol.AbstractProtocolFilterChain$2.messageReceived(AbstractProtocolFilterChain.java:149) > at > org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageReceived(AbstractProtocolFilterChain.java:365) > at > org.apache.mina.protocol.AbstractProtocolFilterChain.access$1000(AbstractProtocolFilterChain.java:50) > at > org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1.messageReceived(AbstractProtocolFilterChain.java:524) > at > org.apache.mina.protocol.AbstractProtocolFilterChain$1.messageReceived(AbstractProtocolFilterChain.java:99) > at > org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageReceived(AbstractProtocolFilterChain.java:365) > at > org.apache.mina.protocol.AbstractProtocolFilterChain.messageReceived(AbstractProtocolFilterChain.java:356) > at > org.apache.mina.protocol.ProtocolSessionManagerFilterChain$1.messageReceived(ProtocolSessionManagerFilterChain.java:77) > at > org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageReceived(AbstractProtocolFilterChain.java:365) > at > org.apache.mina.protocol.AbstractProtocolFilterChain.access$1000(AbstractProtocolFilterChain.java:50) > at > org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1.messageReceived(AbstractProtocolFilterChain.java:524) > at > org.apache.mina.protocol.filter.ProtocolThreadPoolFilter.processEvent(ProtocolThreadPoolFilter.java:108) > at > org.apache.mina.util.BaseThreadPool$Worker.processEvents(BaseThreadPool.java:393) > at > org.apache.mina.util.BaseThreadPool$Worker.run(BaseThreadPool.java:333) -- 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
