Surendar Chandra

Awesome, We were worried about just this scenario (ran into similar issues with other interactions with external services). We pick up artifacts via maven. Any ideas when we will have a public release with this fix? Thanks again

I use the inMemoryLdapServer for some unit tests and call shutdown on them when done. In 4.0.7, it was fine but upgrading to 4.0.11 detects a thread leak of "Write Timeout Handler Timer". What is the best way to it down? Thanks @dirmgr

I'm using a FastestConnectServerSet for my LDAP connection pool. Suppose I have a pool with initialConnections=1, maxConnections=10 and total #servers=20. How many active TCP connections would I see when there is little to no LDAP traffic. I expect 1 TCP + 20 temporary probes but I seem to see way too many TCP connections. On a controlled setup, I only see 1 TCP connection but don't have visibility into when it grows. Thanks again.

May I request that you add the above description to the documentation? Very helpful (the caveats)

Thanks much; that is extremely helpful. So, if I remove schema caching, then I will pay for it in increased network traffic with the same functionality?

I create a connectionpool with initialConnections=1 and maxConnections=numberOfServersInPool. Taking a Java heap dump, each pool seems to take about 14MB for pool, 79MB for Schema and 12MB for healthCheck. Is there any way I can reduce this memory foot print? I do set these options; should I remove them? connectionOptions.setUseSchema(true) connectionOptions.setUsePooledSchema(true)

Thanks Neil. This was specifically to Active Directory but could be any server. I was afraid that I'd have to do what you suggested (because calling search on the connectionpool would've let you internally deal with the particular server going down rather that me deal with it).

I'm doing something like this: connectionPool.search("dc=example,dc=com", SearchScope.SUB, "(uid=john.doe)"); Except, in this deployment, I get a different result, seemingly when I talk to different servers in the pool. Something is not synchronized I suppose. How do I find the server that performed my search. I suppose I can do a connectionPool.getConnection(). Is there another way. Thanks much