[DIRAPI-200] unBind() followed by bind() on the same connection may throw an IllegalStateException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0-M23
• Fix Version/s: 1.0.0-M24
• Assignee: Emmanuel Lécharny
• Reporter: lucas theisen
• Created: 25/Jul/14 19:43
• Updated: 08/Jan/15 17:17
• Resolved: 06/Nov/14 01:13

Description

Not sure if this even should be allowed but the fact that it can result in an exception is disconcerting. I added a test case to LdapConnectionPoolTest (with the unBind() currently commented out) that can be used to reproduce this issue.

The main question here, in my mind, is whether or not this should be allowed. If not allowed, we should immediately throw a more reasonable exception if any operation is attempted on an LdapConnection that has had unBind() called on it. Perhaps still an IllegalStateException, but maybe with a message stating connection no longer valid after unBind(). More importantly, this should happen every time, rather than just when the race condition bears its ugly face. For more discussion, see this email chain.

Issue Links

• is related to: DIRAPI-199 LdapConnectionPool.getUnboundConnection is an oxymoron