Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0.0.AM26
-
None
-
None
Description
In a test setup we regularly saw the warning that an unbind request wasn't processed (see log snippet below). This lead to errors later in our test, as it assumed that the unbind would have been successful.
Looking at the comment in the code of LdapRequestHandler, it reads: "in some cases the session is becoming null though the client is sending the UnbindRequest before closing".
Our workaround attempt is now to enable Java's LDAP connection pooling so that we don't close the LDAP session right after sending the unbind request.
Ideally we would like to see the unbind request being processes regardless of the closed session, as the caller doesn't really have means to determine if the asynchronous processing has completed.
It would be great if ApacheDS would handle this case.
The workaround for Java LDAP connection pooling:
- com.sun.jndi.ldap.connect.pool set to true to enable connection pooling
- com.sun.jndi.ldap.connect.pool.maxsize set to the same value as com.sun.jndi.ldap.connect.pool.prefsize to avoid short-lived connections
The log:
11:05:56,830 INFO [org.apache.directory.server.ldap.handlers.LdapRequestHandler] (pool-26-thread-1) ignoring the message MessageType : UNBIND_REQUEST
Message ID : 3
UnBind Requestorg.apache.directory.api.ldap.model.message.UnbindRequestImpl@cffb7dca ManageDsaITImpl Control
Type OID : '2.16.840.1.113730.3.4.2'
Criticality : 'false'
'
received from null session