[
http://issues.apache.org/jira/browse/JCR-160?page=comments#action_12315546 ]
fabrizio giustina commented on JCR-160:
---------------------------------------
Updated stacktrace with latest svn revision (after the changes in rev. 209739).
Now the exception is thrown directly in the hasNext() method. Note that the
exception occours also while trying to fetch valid nodes, since it's always
thrown while trying to sort nodes in document order.
ERROR org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl
DocOrderNodeIteratorImpl.java(compare:186) 11.07.2005 22:06:44 Exception while
sorting nodes in document order: javax.jcr.ItemNotFoundException:
b14139fb-01ab-492d-a465-e183cb43b484
javax.jcr.ItemNotFoundException: b14139fb-01ab-492d-a465-e183cb43b484
at
org.apache.jackrabbit.core.ItemManager.createItemInstance(ItemManager.java:523)
at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:374)
at
org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl$1.compare(DocOrderNodeIteratorImpl.java:142)
at java.util.Arrays.mergeSort(Arrays.java:1284)
at java.util.Arrays.mergeSort(Arrays.java:1296)
at java.util.Arrays.mergeSort(Arrays.java:1296)
at java.util.Arrays.mergeSort(Arrays.java:1295)
at java.util.Arrays.mergeSort(Arrays.java:1296)
at java.util.Arrays.mergeSort(Arrays.java:1296)
at java.util.Arrays.sort(Arrays.java:1223)
at
org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl.initOrderedIterator(DocOrderNodeIteratorImpl.java:136)
at
org.apache.jackrabbit.core.query.lucene.DocOrderNodeIteratorImpl.hasNext(DocOrderNodeIteratorImpl.java:95)
> Query index not in sync with workspace
> --------------------------------------
>
> Key: JCR-160
> URL: http://issues.apache.org/jira/browse/JCR-160
> Project: Jackrabbit
> Type: Bug
> Components: query
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Fix For: 1.0
>
> After some time the search index is not in sync anymore with the data in the
> workspace and returns uuids which have no corresponding Node in the
> workspace. This results in a NodeIterator which throws an
> ItemNotFoundException on nextNode().
> Instructions how to reproduce this error are not yet available.
> Possible areas for further investigation are:
> - NodeType registry which maps the node types into the workspace with the use
> of virtual item states
> - versioning?
> - atomicity of indexing?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
