[ https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374342#comment-16374342 ]
Thomas Mueller commented on SLING-7169: --------------------------------------- As for index definitions to be installed and queries to run: I would recommend installing the indexes and running the queries in /tmp/waitingIndexingDone. Then the index definitions (two of them): {noformat} /tmp/waitingIndexingDone/oak:index/ testIndexAsync (oak:QueryIndexDefinition) type=lucene async=async tags=async indexRules/nt:base/properties/test name=test analyzed=true testIndexFulltextAsync (oak:QueryIndexDefinition) type=lucene async=fulltext-async tags=fulltextAsync indexRules/nt:base/properties/test name=test analyzed=true {noformat} So this covers the "async" and "fulltext-async" lanes. Queries: {noformat} /jcr:root/tmp/waitingIndexingDone//*[jcr:contains(@test, '<testVal>')] option(traversal ok, index tag async) /jcr:root/tmp/waitingIndexingDone//*[jcr:contains(@test, '<testVal>')] option(traversal ok, index tag fulltextAsync) {noformat} So the same query, twice; once for the index with tag async, and once for the index with tag fulltextAsync. Before running the query, a randomly named node with a randomly set testVal needs to be created (and removed at the end). The query is re-run until it returns the expected nodes. > 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 > Priority: Major > 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 (v7.6.3#76005)