Diagnosing LDAP connection errors.

Tom Poage tfpoage at ucdavis.edu
Thu Sep 29 19:36:04 BST 2011

On 09/28/2011 04:24 PM, Benji Wakely wrote:
> If you're just after the number of concurrent connections held open simultaneously to a particular LDAP server or group of servers,
> and you just want it for one point in time,
> would netstat on the IdP suffice?
> (Looking for 'ESTABLISHED' connections.)
> --Benji

Interesting idea. Activity is 'bursty' and I found that catching
ESTABLISHED connections all but requires running netstat in a continuous
loop. I did so for a short period of time. Never went above three on
each node--which is what (to me) Scott implied about code contention:
it's not load.

Enabled connection pooling today with minPoolSize=3 and (for the time
being) blockWhenEmpty="false". One of the nodes has LDAP logging set to
DEBUG to watch pool activity. Pool size has not gone above minimum so far.

So now I watch and wait. :-)


More information about the users mailing list