[
https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194682#comment-16194682
]
Robert Munteanu edited comment on SLING-7169 at 10/6/17 2:47 PM:
-----------------------------------------------------------------
{quote}http://localhost:8080/system/sling/monitoring/mbeans/org/apache/jackrabbit/oak.tidy.2.json{quote}
That's probably a more structured approach, and I assume that MBean format is
more or less published API. And I agree with [~kwin] that a implementing as a
rule would be best, but probably as [~volteanu] mentioned this should be done
over HTTP.
_edit_: typo
was (Author: rombert):
{quote}http://localhost:8080/system/sling/monitoring/mbeans/org/apache/jackrabbit/oak.tidy.2.json{quote}
That's probably a more structure approach, and I assume that MBean format is
more or less published API. And I agree with [~kwin] that a implementing as a
rule would be best, but probably as [~volteanu] mentioned this should be done
over HTTP.
> 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)
