jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2434) Occasional IndexingQueueTest failure
Date Sat, 12 Dec 2009 20:57:18 GMT

     [ https://issues.apache.org/jira/browse/JCR-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marcel Reutegger resolved JCR-2434.

       Resolution: Fixed
    Fix Version/s: 2.0.0

There is a problematic thread communication between the indexing queue check timer, which
does MultiIndex.checkIndexingQueue() and the thread that executes the test and does IndexingQueue.waitUntilEmpty().

The timer thread will detect a finished extraction and remove the lucene document from the
indexing queue followed by an index update. The notification about the empty indexing queue
is done *before*  the index is updated.

I've changed the notification a bit and now the waiting thread will be notified after the
index is updated.

Fixed in revision: 889976

> Occasional IndexingQueueTest failure
> ------------------------------------
>                 Key: JCR-2434
>                 URL: https://issues.apache.org/jira/browse/JCR-2434
>             Project: Jackrabbit Content Repository
>          Issue Type: Test
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 2.0.0
> Usually the following assertion fails:
> junit.framework.AssertionFailedError
> 	at junit.framework.Assert.fail(Assert.java:47)
> 	at junit.framework.Assert.assertTrue(Assert.java:20)
> 	at junit.framework.Assert.assertTrue(Assert.java:27)
> 	at org.apache.jackrabbit.core.query.lucene.IndexingQueueTest.testQueue(IndexingQueueTest.java:77)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message