[ https://issues.apache.org/jira/brow...action_12530309 ]

Emmanuel Lecharny commented on DIRSERVER-634:
---------------------------------------------

One more information : while playing with JUnit4, I was slapped in the face 
by this issue again. The pb is that there is a bad bug in JNDI when calling 
a destroySubcontext() with an already deleted entry : JNDI modify the result
Code from NO_SUCH_OBJECT to
LDAP_SUCCESS simply because it consider that, as soon as the base DN is Ok, 
and only the RDN does not exist, then it must be a success !!!

As is, deleting "cn=This does not exist, dc=example, dc=org" will return a N
O_SUCH_OBJECT LdapResult, with a matchedDN = "dc=example, dc=org", and JNDI 
will consider that as there is only one level between the baseDN and the del
eted entry DN, then it's a
success.

Thanks JNDI !!!

> Delete with illegal DN causes client to hang
> --------------------------------------------
>
>                 Key: DIRSERVER-634
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-634
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0-RC3
>         Environment: Sun ONE Directory SDK for Java 4.1
> ApacheDS 1.0 RC 3
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
> Microsoft Windows XP version 5.1 Service Pack 1
>            Reporter: Stefan Zoerner
>            Assignee: Emmanuel Lecharny
>         Attachments: DeletionWithIllegalNameTest.java, DIRSERVER-634.ldif,
 DIRSERVER-634.log
>
>
> A delete operation with an invalid DN causes the client to hang. The expected resu
lt is LDAP error code 34 (INVALID_DN_SYNTAX) (preferred), or 32 (NO_SUCH_OBJECT). Fo
r instance I tried to delete DN "This is an illegal name,dc=example,dc=com" (no attr
ibu
te name in RDN).
> Unfortunately, I was not able to create this situation with JNDI. Its LDAP Provide
r seems to ignore such an operation, there is no Exception at all. A Java test case 
created with Sun ONE Directory SDK for Java caused the client to hang, and does not 
pro
duce the result code expected. I'll attach it to this issue.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[ Post a follow-up to this message ]