[jira] [Resolved] (DIRAPI-135) The connectiosn may be invalid when we get it from the pool

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRAPI-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRAPI-135.
--------------------------------------

    Resolution: Fixed

This as been fixed in the 1.0.0-M17 release.

When  the pool uses the testOnBorrow flag set to true, like in :

        pool.setTestOnBorrow( true );

then the connection is checked by fetching an entry from the remote server, before it's returned back to the user. If the connection is not valid, we create a new one.

                
> The connectiosn may be invalid when we get it from the pool
> -----------------------------------------------------------
>
>                 Key: DIRAPI-135
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-135
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M16
>            Reporter: Emmanuel Lecharny
>            Priority: Critical
>             Fix For: 1.0.0-M17
>
>
> When a connection is get from the LdapConnectionPool, it may be invalid (for instance, if the connection timed out). In M16, we don't check that the connection can still 'talk' to the server.
> We need to validate the connection when we request some from the pool

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira