You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/10/15 18:56:43 UTC
[jira] [Created] (SLING-3177) Cache hc result in jmx bean
Carsten Ziegeler created SLING-3177:
---------------------------------------
Summary: Cache hc result in jmx bean
Key: SLING-3177
URL: https://issues.apache.org/jira/browse/SLING-3177
Project: Sling
Issue Type: Improvement
Components: Health Check
Affects Versions: Health Check JMX 1.0.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Health Check JMX 1.0.6
If a client of an hc mbean invokes separately the getAttribute method and retrieves each attribute one by one, this currently results in the hc executed for each call. While this might be inline with jmx guidelines, its not the best idea to execute the hc on each call, especially if the hc is time consuming or resource consuming.
Therefore the hc mbean should cache the result for a very short period of time. This has the benefit of reducing server load.
This is especially important as there is many client code out there, retrieving attributes one by one instead of getting them all by once - and we can't fix all client code
--
This message was sent by Atlassian JIRA
(v6.1#6144)