You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2017/05/04 14:01:04 UTC

[jira] [Commented] (SLING-5952) Add support for configurable SO and connection timeouts

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

Tommaso Teofili commented on SLING-5952:
----------------------------------------

I've fixed this in r1793803.

> Add support for configurable SO and connection timeouts
> -------------------------------------------------------
>
>                 Key: SLING-5952
>                 URL: https://issues.apache.org/jira/browse/SLING-5952
>             Project: Sling
>          Issue Type: Improvement
>          Components: Content Distribution
>    Affects Versions: Content Distribution Core 0.1.18
>            Reporter: Timothee Maret
>            Assignee: Tommaso Teofili
>             Fix For: Content Distribution Core 0.2.8
>
>         Attachments: SLING-SLING-5952.0.patch
>
>
> Currently the SDC transport is using the default HTTP client timeouts
> 1. Connection Timeout (by default it is infinite)
> 2. SO Socket Timeout (by default it is infinite)
> Allowing to configure a bounded timeouts is needed in most deployments in order to avoid leaving a resource stuck.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)