[jira] [Commented] (HTTPCLIENT-1864) [OSGi] Allow to configure the OSGi client default timeouts

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Commented] (HTTPCLIENT-1864) [OSGi] Allow to configure the OSGi client default timeouts

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111141#comment-16111141 ]

Julian Sedding commented on HTTPCLIENT-1864:
--------------------------------------------

[~marett] I have an experimental bundle with support for injecting pre-configured HttpClient instances via OSGi service registry (install in addition to httpclient-osgi). Check out https://github.com/code-distillery/httpclient-configuration-support and let me know if that looks interesting. I am planning to contribute this back to the httpclient-osgi project once I am happy with it and when I find the time.

> [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
>            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: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...