[jira] [Commented] (DIRAPI-89) EntryCursorImpl loops forever in next() when using AD Server with referrals

["Alex Karasulu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DIRAPI-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291445#comment-13291445 ] 

Alex Karasulu commented on DIRAPI-89:
-------------------------------------

AD Server = Active Directory Server, or Apache Directory Server?
                
> EntryCursorImpl loops forever in next() when using AD Server with referrals
> ---------------------------------------------------------------------------
>
>                 Key: DIRAPI-89
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-89
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M12
>         Environment: Mac
>            Reporter: Dave Briccetti
>              Labels: ActiveDirectory, cursor
>
> Search for a user that doesn’t exist on AD. Cursor provides four referrals, but no SearchResultDone.
> val searchArg = "(&(objectclass=%s)(samaccountname=%s))".format(s.objectClass, user)
> val cursor = connection.search(s.baseDn, searchArg, SearchScope.SUBTREE, "*")
> next() hangs in this loop ending on line 102:
>             while ( !( response instanceof SearchResultDone ) );
> Using this code instead causes a SearchResultDone to appear after three referrals:
> val searchRequest = new SearchRequestImpl().setBase(new Dn(s.baseDn))
>   .setFilter(searchArg).setScope(SearchScope.SUBTREE).addControl(new ManageDsaITImpl())

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira