[jira] [Updated] (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:all-tabpanel ] Tommaso Teofili updated SLING-5952: --- Attachment: SLING-SLING-5952.0.patch attaching trivial patch with fixed socket / connect timeout of 10s. > 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: Timothee Maret > 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)
[jira] [Updated] (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:all-tabpanel ] Timothee Maret updated SLING-5952: -- Fix Version/s: (was: Content Distribution Core 0.2.6) Content Distribution Core 0.2.8 > 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: Timothee Maret > Fix For: Content Distribution Core 0.2.8 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Timothee Maret updated SLING-5952: -- Fix Version/s: (was: Content Distribution Core 0.2.4) Content Distribution Core 0.2.6 > 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: Timothee Maret > Fix For: Content Distribution Core 0.2.6 > > > 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)
[jira] [Updated] (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:all-tabpanel ] Timothee Maret updated SLING-5952: -- Fix Version/s: (was: Content Distribution Core 0.2.0) Content Distribution Core 0.2.2 > 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: Timothee Maret > Fix For: Content Distribution Core 0.2.2 > > > 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)
