You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Julian Sedding (JIRA)" <ji...@apache.org> on 2017/08/02 15:57:01 UTC
[jira] [Assigned] (HTTPCLIENT-1864) [OSGi] Allow to configure the OSGi client default timeouts
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Sedding reassigned HTTPCLIENT-1864:
------------------------------------------
Assignee: Julian Sedding
> [OSGi] Allow to configure the OSGi client default timeouts
> ----------------------------------------------------------
>
> Key: HTTPCLIENT-1864
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1864
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (classic)
> Affects Versions: 4.5
> Reporter: Timothee Maret
> Assignee: Julian Sedding
> Priority: Minor
> Fix For: Stuck
>
>
> The OSGI HTTP client currently comes with default connection and socket timeouts.
> The default timeouts are infinite values. Those infinite timeouts imply that a failing connection may hang forever wasting the associated resources and potentially causing the process to stop with hardly reproducible issues.
> There already is a way to configure the timeouts per client instance. This approach provides a great flexibility but it comes at the cost of I. tedious and error prone configurations, II. not solving the issue once for all (new components may forget to add support for timeouts).
> Allowing to configure the default globally or via the factory configuration (with defaults) would give a simpler configuration overall and inherit the configurable default to all consumers of the client.
> This improvement shall only applies to the OSGI client.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org