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 2014/06/03 15:18:03 UTC
[jira] [Resolved] (HTTPCLIENT-1504) Hanging request execution when
PoolingHttpClientConnectionManager has 0 MaxTotal connections set
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-1504.
-------------------------------------------
Resolution: Fixed
Fixed in HttpCore trunk (pre 4.4a1)
Oleg
> Hanging request execution when PoolingHttpClientConnectionManager has 0 MaxTotal connections set
> ------------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-1504
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1504
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Affects Versions: 4.3.2
> Reporter: Aaron Baff
> Priority: Minor
> Fix For: 4.4 Alpha1
>
>
> By mistake, I intialized a PoolingHttpClientConnectionManager with MaxTotal and DefaultMaxPerRoute as 0. When making trying to execute an HttpGet, the request would sit there hung. Turns out, way down in AbstractConnPool, it performs some checks so that if the pool is exhausted, it will queue up this request for a connection, then blocks the current thread (unless there is a timeout given) indefinitely.
> Perhaps throw an error when creating a Connection Pool if either MaxTotal or DefaultMaxPerRoute are <= 0 in order to ensure that accidentally setting bad values such as those will be obvious.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org