directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charlie Barnett (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-1860) Invalid DN in returned entry
Date Mon, 24 Jun 2013 17:26:20 GMT


Charlie Barnett commented on DIRSERVER-1860:

FYI - Pretty sure I tried m12 after reporting issue and got same results. Have tried creating
a test case and also installing source following documentation on site but have not been very
successful with either. Is there a proper place to get help with build issues? Not a critical
issue for me but I am curious about the process.
> Invalid DN in returned entry
> ----------------------------
>                 Key: DIRSERVER-1860
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>         Environment: Windows Server 2008 R2 Standard
>            Reporter: Charlie Barnett
>            Priority: Minor
>             Fix For: 2.0.0-M11
> I am trying to match entries in two directories and produce an xml file of differences.
ApacheDS is the server for both directories. JXplorer is being used to modify one of the directories.
The modified directory is read using a SearchResultListener. In one case the dn of the SearchResultEntry
passed to the listener is incorrect. It only contains the rdn of the entry. The specific case
is when a new uniqueMember is added to an existing entry of type groupOfUniqueNames. This
occurs with both JXplorer and also with Apache Directory Studio. After starting and stopping
the server the correct dn is contained in the entry passed. Waiting aproximately 15 minutes
also clears the problem. Am using unboundid ldap client library
> Reported problem initially to unboundid but determined by running a proxy that the invalid
dn was being returned from server. Link to unboundui report is

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

View raw message