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 2019/12/19 13:12:00 UTC
[jira] [Resolved] (HTTPCLIENT-2039) Do not close ConnectionManager
in case of Errors
[ https://issues.apache.org/jira/browse/HTTPCLIENT-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-2039.
-------------------------------------------
Resolution: Won't Fix
> Do not close ConnectionManager in case of Errors
> ------------------------------------------------
>
> Key: HTTPCLIENT-2039
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2039
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (classic)
> Affects Versions: 4.5.10
> Reporter: Thomas Sartissohn
> Priority: Minor
>
> The MainClientExec closes the connectionManager in the execute method whenever a java error is received. In my case an OutOfMemoryError was thrown. This ended in a client instance no longer usable cause the pool was already shut down. And therefore the real error (OutOfMemoryError) was covered by many "Connection pool shut down" exceptions.
> I agree that the OutOfMemoryError is a severe issue which should be covered somehow. But closing the pool is unexpected here.
> Is there a chance to remove the closing part and keep the pool running in error case?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org