directory-api mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn McKinney <>
Subject LdapConnectionPool.getConnection doing extraneous search?
Date Sat, 20 Mar 2021 21:57:41 GMT

I’m using LDAP API v1.0.3 inside fortress.  

My question is when retrieving connections from the pool using this:

public LdapConnection getConnection()

Gives a LdapConnection fetched from the pool.

    an LdapConnection object from pool

I noticed in the OpenLDAP logs (filter and stats enabled) an extra search comes through during
this invocation:

Begin slapd log trace:

[exec] 60566cd5 begin get_filter
[exec] 60566cd5 PRESENT
[exec] 60566cd5 end get_filter 0
[exec] 60566cd5 conn=1010 op=5 SRCH base="" scope=0 deref=3 filter="(objectClass=*)"
[exec] 60566cd5 conn=1010 op=5 SRCH attr=1.1
[exec] 60566cd5 => test_filter
[exec] 60566cd5     PRESENT
[exec] 60566cd5 <= test_filter 6
[exec] 60566cd5 conn=1010 op=5 SEARCH RESULT tag=101 err=0 duration=0.236ms nentries=1 text=

It’s performing a null base search with objectClass=* asking for attr ‘1.1'.

What’s going on here?  I expect to see a bind on that connection (the first time) but not
a search.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message