[
https://issues.apache.org/jira/browse/DIRAPI-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lucas theisen closed DIRAPI-199.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0-M24
removed {{getUnboundConnection()}}
revision: 1613509
> LdapConnectionPool.getUnboundConnection is an oxymoron
> ------------------------------------------------------
>
> Key: DIRAPI-199
> URL: https://issues.apache.org/jira/browse/DIRAPI-199
> Project: Directory Client API
> Issue Type: Bug
> Reporter: lucas theisen
> Priority: Critical
> Fix For: 1.0.0-M24
>
>
> 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|http://mail-archives.apache.org/mod_mbox/directory-dev/201407.mbox/%3CEE6ADC61AF2D71408E4FA7F9517DB7710A9C07E5%40IMCMBX03.MITRE.ORG%3E]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
