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] (HTTPCORE-378) AbstractConnPool should perform expired entries clean up outside of lock
Date Thu, 24 Apr 2014 14:38:15 GMT

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

Oleg Kalnichevski resolved HTTPCORE-378.

    Resolution: Won't Fix

> AbstractConnPool should perform expired entries clean up outside of lock
> ------------------------------------------------------------------------
>                 Key: HTTPCORE-378
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-378
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore
>    Affects Versions: 4.3.2
>            Reporter: Dmitry Potapov
>            Priority: Trivial
> Currently expired entries are closed at AbstractConnPool.getPoolEntryBlocking:230. If
connections have non-zero SO_LINGER enabled this will cause other threads to wait up to SO_LINGER
> Unfortunately same reentrant lock is already held by PoolEntryFuture.get(), so list of
pool entries to be closed must be accumulated but some external queue and processed by additional
> There is workaround for this issue for http-clients: apply patches from HTTPCORE-377
and HTTPCLIENT-1497 and set SocketConfig.setSoLinger(0).
> Since this issue has workaround, I suggest to consider this issue as very low priority

This message was sent by Atlassian JIRA

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

View raw message