[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194464#comment-16194464 ]
Alex Deparvu commented on SLING-7169: ------------------------------------- I'm really not familiar with the sling options here, but I know there was an issue recently to expose the same info via the inventory plugin (OAK-6215). does the following link work for you? [0] bq. There are multiple indexing lanes and you have to know for which one to wait. yes, here we're probably going to need to monitor the 'async=async' lane [0] http://localhost:4502/system/console/status-oak-index-stats.json > 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)