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] [Updated] (HTTPCLIENT-1504) Hanging request execution when PoolingHttpClientConnectionManager has 0 MaxTotal connections set
Date Sat, 31 May 2014 14:47:02 GMT

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

Oleg Kalnichevski updated HTTPCLIENT-1504:
------------------------------------------

    Fix Version/s: 4.4 Alpha1

> 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


Mime
View raw message