Neil Wilson

Thanks for reporting this. I've committed a fix.

A connection pool should never close (or do anything else with) a connection that has been checked out of the pool. The pool wouldn't even have a reference to that...

Actually, from taking a closer look at the error message you're getting back, it seems like you're using asynchronous operations. Those are very difficult to get right when you're using...

And to answer your question about a maximum connection age of zero, that is documented in the javadoc for the setMaxConnectionAgeMillis method: "A value of zero indicates that no maximum...

A connection pool should never attempt to close a connection because of the maximum age while it’s checked out of the pool. The pool only looks at a connection’s age...

Yes, the problem is that you’re calling releaseConnection before the search has completed. Releasing the connection tells the pool that it’s free to do whatever it wants with that connection,...

LDAP SDK releases are published in the Maven central repository with a group ID of "com.unboundid". The Standard Edition has been published there since version 1.1.1 and has an artifact...

If you've found a bug in the code, then please report it so that it can be fixed. I don't understand why you think that creating your own fork is...

I've just committed a change that updates SearchRequest to provide variants of the constructor that take DN objects as an alternative to Strings. I hadn't added those in the first...

The LDAP SDK is throwing this exception because it has received an error response from Active Directory. The text of the exception "000020E6: SvcErr: DSID-031406E4, problem 5012 (DIR_ERROR), data 700"...