directory-api mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <>
Subject Re: LdapConnectionPool.getConnection doing extraneous search?
Date Tue, 23 Mar 2021 08:00:11 GMT

On 22/03/2021 19:41, Shawn McKinney wrote:
>> On Mar 22, 2021, at 11:05 AM, Emmanuel Lécharny <> wrote:
>> LDAP connections are quite stable. Again, this check is there to respect the commons-pool
API contract. If the connection is dead, then doing this check will let the pool fetching
another connection, which is good. OTOH, if you don't want to check connections while fetching
one, then you are on your own (ie, deal with the consequences of a bad connection).
> Again, I must disagree.  Connections aren’t stable, subjected to env conditions and
we can never assume a connection is good. 

You *can* assume it's good, and react exceptionally if it's not. That 
the fastest way to deal with potential bad connections, if you want to 
avoid a check every time you pull a connection from the pool. (but see 
later for another option)

  Something in the API chain must do the job of testing and reconnect, 
every time it’s pulled from the pool.

This is exactly what the testOnBorrow does ;-) But it's costly... (see 
later for another option)

> Now, having said that, that’s exactly what I’m observing currently, with the test
on borrow flag turned off.
> Let me explain the scenario:
> 1. Start server
> 2. Start client
> This initializes a connection pool which creates and stores exactly 1 connection (min
1, max1 )
> 3. Set breakpoint in client on pool.getConnection method
> 4. Restart the server.
> 5. Client performs ldap op which triggers the breakpoint on getConnection
> 6. Server at this point still hasn’t any connections with the client.  The client ‘thinks’
it has connections in the pool, but these were broken on step 4.
> 7. Step over the getConnection which then triggers the commons pool to execute:
> ```                GenericObjectPool._factory.activateObject(latch.getPair().value)
> ```
> 8. A connection is made with the server, along with bind
> ```
> 6058e163 conn=1000 fd=14 ACCEPT from IP= (IP=
>       [exec] 6058e163 conn=1000 op=0 BIND dn="cn=manager,dc=example,dc=com" method=128
>       [exec] 6058e163 conn=1000 op=0 BIND dn="cn=manager,dc=example,dc=com" mech=SIMPLE
>       [exec] 6058e163 conn=1000 op=0 RESULT tag=97 err=0 duration=1.667ms
> ```
> 9. Client continues with its ldap op successfully and is never the wiser that the connections
were all forcibly closed on server restart.
> This is EXACTLY what I want to see all of which is done without the test on borrow eliminating
the extraneous search on every connection retrieval.

So that would mean we have some kind of 'retry' on connection operation: 
if it fails, then let's assume the connection is broken, and redo it 
with a fresh connection.

The problem is that the pool is passive: it does not react to any 
connection event, like a connection closure. OTOH, when a connection is 
properly closed by the server (ie an NoticeOfDisconnect - aka NoD - is 
generated by the server), the connection should process it and die. Now 
we have an issue: the connection is just lying in the pool, not being 
used by any client, so there is a missing step: removing the connection 
from the pool in this very case. That can be something we can add to the 
current LDAP pool.

Note that if the server does not send a NoD, you are screwed. There is 
no way to be sure that the connection is ok until you use it. OTOH, 
leveraging the setTestWhileIdle() could be a solution to partially 
workaround the issue.

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

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

View raw message