[
https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311340#comment-16311340
]
Thomas Mueller commented on SLING-7169:
---------------------------------------
I wouldn't use the JMX bean, as that might change in the future.
What I would do is: create a method "waitForAsyncIndex", and call that before
you run queries. That way, you will only have to call this method, and if
changes are needed, change this method. In that method, do the following:
* Add a node "/temp/node<random>", with indexed property set to a random value.
Ensure a fulltext index can be used for this content.
* In a lop, do the following
* Query for that node using something like
{{/jcr:root/tmp//*\[jcr:contains($value)] option(traversal fail)}}.
* The "option(traversal fail)" will ensure the query fails with an exception if
the index is not initialized
* If the newly added node is return, end the loop
* Remove the temporary node
> 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)
