[
https://issues.apache.org/jira/browse/SLING-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170531#comment-15170531
]
ASF GitHub Bot commented on SLING-4941:
---------------------------------------
GitHub user ghenzler opened a pull request:
https://github.com/apache/sling/pull/126
SLING-4941 integration test for jmx-adjustable HC for testing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ghenzler/sling SLING-4941-integration-test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/126.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #126
----
commit 4d7013e1a3546fe9bae62c0095c4192e24128560
Author: georg.henzler <[email protected]>
Date: 2016-02-26T22:37:07Z
SLING-4941 integration test for jmx-adjustable HC for testing
----
> JMX-configurable OK/NOK-Check for testing purposes
> --------------------------------------------------
>
> Key: SLING-4941
> URL: https://issues.apache.org/jira/browse/SLING-4941
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
> Reporter: Georg Henzler
> Assignee: Carsten Ziegeler
> Fix For: Health Check Core 1.2.4
>
> Attachments: JMX-adjustable-HC-for-testing.png,
> SLING-4941-JMX-adjustable-HC.patch
>
>
> For testing purposes (infrastructure tests with load balancers etc.) it can
> be useful to make the result for a given tag(s) fail manually.
> There are two options:
> # provide a check that is configurable via JCR (using metatype
> configuration).
> # provide a check that can be dynamically added via JMX
> The second options is IMHO nicer, because it's easier to run a JMX operation
> (compared to adding/changing a configuration in JCR). Also if this feature is
> not being used, it should not clutter the list of available health checks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
