hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HTTPASYNC-28) PoolEntry's expiry information is never updated
Date Thu, 27 Sep 2012 11:34:11 GMT

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

Oleg Kalnichevski resolved HTTPASYNC-28.

       Resolution: Fixed
    Fix Version/s: 4.0-beta4

Good catch, Daniel. Patch checked in. Thank you. 

How critical do you deem this fix to be for the coming CXF release? I was about to close 4.0b3
release vote based on RC1, which does not include this fix. Would you like me to call off
the release and cut a new RC off the latest trunk?

> PoolEntry's expiry information is never updated
> -----------------------------------------------
>                 Key: HTTPASYNC-28
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-28
>             Project: HttpComponents HttpAsyncClient
>          Issue Type: Bug
>            Reporter: Daniel Kulp
>             Fix For: 4.0-beta4
>         Attachments: patch.txt
> The PoolingClientAsyncConnectionManager.releaseConnection method calls managedConn.detach()
which detaches the entry.  However, it then calls "isOpen" on it which requires it to be attached
in order to determine if it's open or not.   With it not open, the expiry values are never

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

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

View raw message