[jira] [Commented] (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:comment-tabpanel=16114151#comment-16114151 ] Timothee Maret commented on HTTPCLIENT-1864: Thanks [~olegk] for your input. I agree, there's already a client builder configurator. However, I think we still miss a way to configure default for the client in a central way, similarly to what exists for the proxy configuration. Thanks [~jsedding] for sharing, I'll have a look. > [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-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
[jira] [Commented] (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:comment-tabpanel=1641#comment-1641 ] 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: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
