directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-634) Delete with illegal DN causes client to hang
Date Thu, 03 Aug 2006 23:45:15 GMT
    [ ] 
Emmanuel Lecharny commented on DIRSERVER-634:

Well, it's not so clear. Here is a status :

1) bytes arrive from the client.
2) ASN.1 codec is called
3) The request  is analyzed by TwixDecoder
4) If there is a DN, it is parsed 
 4-1) If the DN is wrong, then a DecoderException is generated, so the client receive a Protocol
Error instead of a LdapResult
 4-2) Else, we pass the request to TwixTransformer
5) TwixTransformer transform a TwixRequest to a SnickersMessage
 and here is tyhe problem : SnickersMessage hold a LdapDN, too. So we can't wait until we
reach the Handler to check that the DN is correct or not.

Rrrrrrahhhhhh !!!! We have to find a solution which does not implies that we don't rewrite
*all* the snickezrs and twix messages ...

> 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
>         Assigned To: Emmanuel Lecharny
>         Attachments:, DIRSERVER-634.ldif, DIRSERVER-634.log
> 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