directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-634) Delete with illegal DN causes client to hang
Date Sun, 30 Jul 2006 18:41:14 GMT
    [ ] 
Stefan Zoerner commented on DIRSERVER-634:

Yes, I was not able to create the situation with JNDI due to the strange error handling the
API has. 

Please note, that the attached test case passes with the
following products

  * Sun Java System Directory Server 5.2
  * IBM Tivoli Directory Server 6.0
  * OpenLDAP 2.3

and fails with ApacheDS 1.0 RC3. So I do not think it is a client API problem.

One alternative to create a comparable situation is to execute the LDIF file I attach:

$ ldapmodify -D "uid=admin,ou=system" -w ****** -f DIRSERVER-634.ldif

It causes a protocol error on Apache DS (log file is attached as well), which I assume is
the origin of the original error described in this issue.

> Delete with illegal DN causes client to hang
> --------------------------------------------
>                 Key: DIRSERVER-634
>                 URL:
>             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
>         Attachments:
> A delete operation with an invalid DN causes the client to hang. The expected result
is LDAP error code 34 (INVALID_DN_SYNTAX) (preferred), or 32 (NO_SUCH_OBJECT). For instance
I tried to delete DN "This is an illegal name,dc=example,dc=com" (no attribute name in RDN).
> Unfortunately, I was not able to create this situation with JNDI. Its LDAP Provider 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 produce the result code
expected. I'll attach it to this issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message