[
https://issues.apache.org/jira/browse/DIRAPI-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRAPI-217.
--------------------------------------
Resolution: Fixed
> Under heavy load, the Connection Pool will not provide valid connections
> ------------------------------------------------------------------------
>
> Key: DIRAPI-217
> URL: https://issues.apache.org/jira/browse/DIRAPI-217
> Project: Directory Client API
> Issue Type: Bug
> Affects Versions: 1.0.0-M27
> Reporter: Emmanuel Lecharny
> Priority: Blocker
> Fix For: 1.0.0-M28
>
>
> What happens is that when a lot of threads are requesting connections from
> the pool, and if the number of idle connections get above the max idle
> connections configure for the pool, then some connections will be mandatory
> closed by the pool, and may remain in a transient state for a bit of time,
> and be allocated to a thread.
> This is due to the fact we don't wait for the complete closure of a
> connection when we do a session.close(), which returns a CloseFuture.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
