|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
ldap inconsistent search results
Submitted by ghotik on Thu, 03/05/2009 - 13:30.
Tags:
I'm getting mixed results when I do a search to LDAP. I found that it has to do with how much time I wait between calling LDAPConnection.search() and LDAPSearchResults.next(). For my situation the sweet spot is to sleep 100 millis (Thread.sleep(100)) before calling next(). This gives me a 50% chance of a hit or a miss for the same search base on a good connection.
Is there a way tell the search to block until complete or to implement a reliable ready() function for LDAPSearchResults similar to the one in BufferedReader?
Oh, and here is the entry in my pom:
<dependency>
<groupId>com.novell.ldap</groupId>
<artifactId>jldap</artifactId>
<version>4.3</version>
</dependency>