[DIRAPI-199] LdapConnectionPool.getUnboundConnection is an oxymoron

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.0.0-M24
• Assignee: Unassigned
• Reporter: lucas theisen
• Created: 25/Jul/14 19:34
• Updated: 25/Jul/14 20:16
• Resolved: 25/Jul/14 20:16

Description

The unBind() operation, will close the session, thereby disconnecting, so you are effectively handing out an unconnected connection. This makes no sense. The best thing to do in this case is most likely to just hand out an already bound connection because that is the only guarantee we can make with a pool other than creating a new connection each time. When a connection is returned to the pool, we can just re bind() it so as to make sure that any changes made to the connection are reverted back to an initial state.

Furthermore, an unBind() followed shortly thereafter by a bind() will eventually cause a race condition as described here

Issue Links

• relates to: DIRAPI-200 unBind() followed by bind() on the same connection may throw an IllegalStateException