On 12/26/2014 07:02 PM, Emmanuel Lécharny wrote: > So bottom line, there is a workaround : set maxIdle to -1, but the drawback > is that we may have a growing pool size if the connections are never released > and put back to the pool. The other workaround is to set this parameter to a > value abve the number of thread (not easy to determinate).
Tested the workaround and it works in fortress core. Agree this needs to be solved, but is no longer a show stopper for us. The good news is fortress throughput using apache ldap api now far exceeds unbound id's ldap client. I want to run more tests before publishing numbers but the apache ldap api is fast!
