[
https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194395#comment-16194395
]
Julian Sedding commented on SLING-7169:
---------------------------------------
[~rombert] Via {{org.apache.sling.jmx.provider}} there's a {{ResourceProvider}}
exposed at {{/system/sling/monitoring/mbeans}}. Not sure this is installed in
your test. But you should then be able to access the resources via the default
GET servlet, e.g.
http://localhost:8080/system/sling/monitoring/mbeans/org/apache/jackrabbit/oak.tidy.2.json.
Note that I didn't manage to access the child resource {{"IndexStats"}}
directly, possibly because of the quotes.
> FullTextIndexingTest sometimes fails with a timeout
> ---------------------------------------------------
>
> Key: SLING-7169
> URL: https://issues.apache.org/jira/browse/SLING-7169
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Reporter: Robert Munteanu
> Labels: sling-IT
> Attachments: SLING-7169-logs.tar.gz
>
>
> The test fails maybe 1 in 10 runs. I could reproduce this locally by running
> many times. I've also seen it once on Jenkins.
> **Old description below**
> After upgrading the launchpad to commons.threads 3.2.10 the
> FullTextIndexingTest failed ( [build
> 1547|https://builds.apache.org/job/sling-launchpad-testing-1.8/1547/] ).
> I also reproduced it once locally.
> [~kwin] - since the commons.threads release is the potential root cause, can
> you please take a look at the failure and see if it's related?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
