You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2014/11/06 02:19:34 UTC
[jira] [Resolved] (DIRAPI-208) The Connection Pool is a bit too
aggressive when it comes to validate connections
[ https://issues.apache.org/jira/browse/DIRAPI-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRAPI-208.
--------------------------------------
Resolution: Fixed
Fixed with http://svn.apache.org/r1637004
> The Connection Pool is a bit too aggressive when it comes to validate connections
> ---------------------------------------------------------------------------------
>
> Key: DIRAPI-208
> URL: https://issues.apache.org/jira/browse/DIRAPI-208
> Project: Directory Client API
> Issue Type: Improvement
> Affects Versions: 1.0.0-M24
> Reporter: Emmanuel Lecharny
> Fix For: 1.0.0-M25
>
>
> Atl, when we pull a connection from the Pool, this connection gets validated, which requires a roundtrip to the server. It's also re-bound when we release the connection, which is another roundtrip to the server.
> We need a lighter config factory for the pool, that does not do such roundtrips, but assume that if the connection is still up, then we can reuse it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)