fpav00

Hi Neil, thank you very much for your answer. You are completely right - the issue was with bind request. I have added bind request to Failover server set as well as to connection pool and everything is fine, it is behaving as it should. Thank you again, BRs

Hi Neil, firstly, thank you very much for your comment. I also tried reproducing this issue in local environment using LDAP SDK's in-memory-directory servers and failed to reproduce the issue. I am using 4.0.10. I will update it and comment back here. I will also post later some of the logs I get when running it in environment with OpenLDAP servers. I am not sure, but just a thought: if the server sends EC 52, will the connections be considered closed and server not connectable? Also, I am trying...

I am trying to use failover server set. In my environment, I have 2 OpenLDAP servers up and running. I am connecting to them in depicted fashion: //////////////////////////////////////////////////////////////// String[] addresses = {"address1", "address2"}; int[] ports = {111, 222}; LDAPConnectionOptions options = new LDAPConnectionOptions(); options.setConnectTimeoutMillis(1000); options.setResponseTimeoutMillis(2000); options.setAbandonOnTimeout(true); options.setUseReuseAddress(false) options.setUseKeepAlive(false);...