You are viewing a plain text version of this content. The canonical link for it is here.

Posted to server-dev@james.apache.org by "ouvtam (Jira)" <se...@james.apache.org> on 2022/11/03 07:39:00 UTC

[jira] [Updated] (JAMES-3849) WebAdmin: Cache health checks

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

ouvtam updated JAMES-3849:
--------------------------
    Priority: Minor  (was: Major)

> WebAdmin: Cache health checks
> -----------------------------
>
>                 Key: JAMES-3849
>                 URL: https://issues.apache.org/jira/browse/JAMES-3849
>             Project: James Server
>          Issue Type: Improvement
>          Components: webadmin
>            Reporter: ouvtam
>            Priority: Minor
>
> While working on JAMES-3841 I noticed that a health check (e.g. ActiveMQ) is called periodically and for each WebAdmin request (i.e. [http://localhost/healthcheck).] This assumes that a health check call should be cheap, but might not be.
> So calling /healthcheck too regularly can produce pressure for the underlying service (e.g. ActiveMQ) that could lead to resource waste or loss of reliability.
> I propose to cache the healthcheck results for WebAdmin (e.g. 5 seconds). What do you think?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org