[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: JLDAP: No results on multiple synchronous searches
- To: openldap-software@OpenLDAP.org
- Subject: Re: JLDAP: No results on multiple synchronous searches
- From: "Marc Boorshtein" <mboorshtein@gmail.com>
- Date: Wed, 5 Jul 2006 07:02:00 -0400
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JGClyeopEX1TFcP6z1YH4JGWDQ9Ks/HdQEohFmiFbdsTIcEpyAB5lMSfnL/NXXlNuv5Z8Zu9YZ3yebSzl0LEAcrmy3bMb13AYrzBxOqqXxbJYHM4jRkepmFciEOPCeG1eoySIvN+PNiJ+2qg6kEVyru1zlyfchHgmk2+fI8sYBs=
- In-reply-to: <44A5AB25.4040402@jonanddeb.net>
- References: <200606292337.k5TNbRrX004730@Den.BOFH.Ca> <44A5AB25.4040402@jonanddeb.net>
> I did see that. I did understand it. However, I also do not see any
> methods via LDAPSearchResults to indicate when the response has been received.
Correct, the implementation is hidden from you on a synchronous search
> As I said in my post, if I use next(), I get an exception. I don't get an
> exception along the lines of "EAGAIN", I get 82, LOCAL ERROR.
Are you calling hasMore() first? I'm pretty sure this is required
before you can grab an entry.
Try checking hasMore() before calling next() to avoid errors.
NM, I see Jon's already covered this one.