Rahul Goswami

Yes I did notice that the intermediateResultCode in SearchRequest.java was being overriden if a referral error is received and the SearchResult is wrapped in LDAPSearchException in LDAPConnection.java to throw an error. And that's what led me to think that it would be nice to have a method like searchNoEx() which would just return the SearchResult and not wrap it in an exception. Thanks for the quick help Neil! I will work around this by extracting the underlying SearchResult object in the exception...

Yes I did notice that the intermediateResultCode in SearchRequest.java was being overriden if a referral error is received and the SearchResult is wrapped in LDAPSearchException in LDAPConnection.java to throw an error. And that's what led me to think that it would be nice to have a method like searchNoEx() which would just return the SearchResult and not wrap it in an exception. Thanks for the quick help Neil! I will work around this by extracting the underlying SearchResult object in the exception...

Yes I did notice that the intermediateResultCode in SearchRequest.java was being overriden if a referral error is received and the SearchResult was being wrapped in LDAPSearchException in LDAPConnection.java to throw an error. And that's what led me to think that it would be nice to have a method like searchNoEx() which would just return the SearchResult and not wrap it in an exception. Thanks for the quick help Neil! I will work around this by extracting the underlying SearchResult object in the...

Hi Neil, Thank you very much for the prompt and detailed response. However, from the way you have described it, it appears that I am running into the first case. I say this because the LDAPSearchException that I get contains the SearchResult object with the rest of the entries and that one bad reference (which is causing the exception). For what it's worth, the search scope in my case is SearchScope.ONE and the search filter is (objectClass=*) with referral turned on. Interestingly, JNDI ignores...

Hi Neil, Thank you very much for the prompt and detailed response. However, from the way you have described it, it appears that I am running into the first case. I say this because the LDAPSearchException that I get contains the SearchResult object with the rest of the entries and that one bad reference (which is causing the exception). For what it's worth, the search scope in my case is SearchScope.ONE and the search filter is (objectClass=*) with referral turned on. Interestingly, JNDI ignores...

I am working on a project to replace the current JNDI implementation with UnboundID LDAP SDK. During one of the tests I observed that despite setting the LDAPConnectionOptions.setFollowReferrals(true) I get an LDAPSearchException with resultCode 10 which is a referral error. Upon further investigating the search reference URLs in the exception, I found that one of the referral hosts is not accessible which causes LDAP SDK to register an error and eventually throw an exception. In such a case I would...