You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2011/08/22 17:47:30 UTC

[jira] [Updated] (HTTPCORE-269) Connection pools incorrectly handle lease requests when the max limit for the given route has been exceeded and all connections in the route pool are stateful

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

Oleg Kalnichevski updated HTTPCORE-269:
---------------------------------------

    Affects Version/s: 4.2-alpha1
        Fix Version/s: 4.2-alpha2

> Connection pools incorrectly handle lease requests when the max limit for the given route has been exceeded and all connections in the route pool are stateful
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HTTPCORE-269
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-269
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>    Affects Versions: 4.2-alpha1
>            Reporter: Oleg Kalnichevski
>             Fix For: 4.2-alpha2
>
>
> Connection pools (blocking and non-blocking) incorrectly handle lease requests when the max limit for the given route has been reached or exceeded and all connections in the route pool are stateful. Lease methods should close out stateful connection kept alive in the route pool to make room for new connections. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org