directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kiran Ayyagari <kayyag...@apache.org>
Subject Re: Ldap pool issue...
Date Mon, 29 Dec 2014 00:07:58 GMT
On Mon, Dec 29, 2014 at 12:06 AM, Shawn McKinney <smckinney@apache.org>
wrote:

> 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!
>
that is good to know, with the new codec processor (still in brainstorming
phase) it may become even
more faster


-- 
Kiran Ayyagari
http://keydap.com

Mime
View raw message