You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2012/09/27 13:42:08 UTC
[jira] [Commented] (HTTPASYNC-28) PoolEntry's expiry information is
never updated
[ https://issues.apache.org/jira/browse/HTTPASYNC-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464646#comment-13464646 ]
Daniel Kulp commented on HTTPASYNC-28:
--------------------------------------
Not critical. There is always b4. :-)
> 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 updated.
--
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