sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Sedding (JIRA)" <>
Subject [jira] [Commented] (SLING-7169) FullTextIndexingTest sometimes fails with a timeout
Date Fri, 06 Oct 2017 10:08:00 GMT


Julian Sedding commented on SLING-7169:

[~rombert] Via {{}} 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:
>             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|] ).
> 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

View raw message