[ http://issues.apache.org/jira/browse/DIRSERVER-634?page=all ]
Emmanuel Lecharny resolved DIRSERVER-634.
-----------------------------------------
Resolution: Fixed
Fixed ! A common work with Alex finally terminated this issue. The bad DN thew
an exception, which was not catched. Now, when we get a excpetion while parsing
this DN, we generate a DelResponse where the LdapResult contains the error code.
This should be done for every places where the DN is parsed
> Delete with illegal DN causes client to hang
> --------------------------------------------
>
> Key: DIRSERVER-634
> URL: http://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
> Assigned To: 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
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
