You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Nicolas Peltier (JIRA)" <ji...@apache.org> on 2018/09/13 14:26:00 UTC

[jira] [Resolved] (SLING-7902) The http.conn.timeout property on ForwardDistributionAgentFactory does not pick user entered values.

     [ https://issues.apache.org/jira/browse/SLING-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Peltier resolved SLING-7902.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Content Distribution Core 0.3.0

> The http.conn.timeout property on ForwardDistributionAgentFactory does not pick user entered values.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-7902
>                 URL: https://issues.apache.org/jira/browse/SLING-7902
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>    Affects Versions: Content Distribution Core 0.2.10
>            Reporter: Adityasharma
>            Priority: Major
>             Fix For: Content Distribution Core 0.3.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> As part of one of the projects we were trying to use Sling Content Distribution. Whenever our package size grew to a number which took more than 10 seconds to process our distribution queue on the Author instance would go into a blocked state and was irrecoverable from. We had to manually clean the queue in order to proceed.
> While trying to troubleshoot the issue we tried to increase the http.conn.timeout but this did not take hold. While trying to debug the issue further we came across the file ForwardDistributionAgentFactory and found that this parameter was not being read from the configs and hence getting hard coded to a default value of 10 seconds. 
> On further investigation we found its the same case with the Reverse/Sync Distribution Agent Factory classes too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)