java - LDAP connection pooling: can the context request its connection to be removed from the pool (and closed)?

Question

I have a Java component deployed on a JBoss AS. It uses LDAP connection pooling to connect to an LDAP server backend (it creates javax.naming.directory.InitialDirContext with com.sun.jndi.ldap.connect.pool=true). Pooling works as expected, with the com.sun.jndi.ldap.connect.pool.timeout set to 5 sec: connection is closed by LDAP pool manager when idle for over 5 sec.

Is there a way for my LDAP context to request the connection to be forcefully closed and removed from the pool (or even the whole set of pool connections to be reset) ?

Reason for asking: when the LDAP server backend application is down but the host on which it runs is still healthy, my component LDAP search times out (ReadTimeout exception) and the context is closed. The connection is then returned to the pool manager. However the pool manager does not remove the connection from the pool: when the next context is created, the same connection will be used, producing another timeout. This will go on unless the idle timeout occurs, which is unlikely if there is enough traffic. By forcefully closing the connection, I intend to use DNS to provide a new backend server to connect to (at the next Java DNS cache refresh).

Note: according to the LDAP pooling doc

Bad connections are automatically detected and removed from the pool by the LDAP provider. The probability of a context ending up with a bad connection is the same regardless of whether connection pooling is used.

but i cannot find a definition of "bad connections". The only occurence of connection removal I can see is the idle timeout connection cleanup.

question from:https://stackoverflow.com/questions/65876259/ldap-connection-pooling-can-the-context-request-its-connection-to-be-removed-fr

Answer 1

Waitting for answers