You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/07/19 10:49:20 UTC
[jira] [Assigned] (SLING-5867) SlingRequestStatusHealthCheck should
add timeout support
[ https://issues.apache.org/jira/browse/SLING-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus reassigned SLING-5867:
--------------------------------------
Assignee: Konrad Windszus
> SlingRequestStatusHealthCheck should add timeout support
> --------------------------------------------------------
>
> Key: SLING-5867
> URL: https://issues.apache.org/jira/browse/SLING-5867
> Project: Sling
> Issue Type: Bug
> Components: Health Check
> Affects Versions: Health Check Support 1.0.4
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
>
> Currently {{o.a.s.hc.support.impl.SlingRequestStatusHealthCheck}} just synchronously calls {{SlingRequestProcessor.processResponse}}.
> That means in case of a non-returning response (e.g. caused by a deadlock like SLING-5847) the health check will just timeout but never actually really fail (even after a very long time).
> In this case it is good to create a dedicated timeout handling within the {{SlingRequestStatusHealthCheck}} (separate from the timeout in {{HealthCheckExecutorImpl}}) because for each individual request health check configuration you might want to set different timeouts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)