Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Health Check Support 1.0.4
-
None
-
None
Description
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.