[ http://issues.apache.org/jira/browse/JCR-160?page=comments#action_12315483 ]
fabrizio giustina commented on JCR-160: --------------------------------------- I got this error once more with revision < 209739: the search index became corrupted after an OutOfMemoryError (note that no write operations were in place when the out of memory occurred, only read). I can't see any particular stacktrace involving the lucene indexer in the out of memory log. Anyway, after restarting the application a write lock on the search index was set and an uncommitted redo log was present: WARN org.apache.jackrabbit.core.query.lucene.PersistentIndex 11.07.2005 14:13:02 -- Removing write lock on search index. WARN org.apache.jackrabbit.core.query.lucene.PersistentIndex 11.07.2005 14:13:02 -- Removing write lock on search index. WARN org.apache.jackrabbit.core.query.lucene.PersistentIndex 11.07.2005 14:13:02 -- Removing write lock on search index. WARN org.apache.jackrabbit.core.query.lucene.PersistentIndex 11.07.2005 14:13:02 -- Removing write lock on search index. WARN org.apache.jackrabbit.core.query.lucene.PersistentIndex 11.07.2005 14:13:02 -- Removing write lock on search index. WARN org.apache.jackrabbit.core.query.lucene.PersistentIndex 11.07.2005 14:13:02 -- Removing write lock on search index. WARN org.apache.jackrabbit.core.query.lucene.MultiIndex 11.07.2005 14:13:02 -- Found uncommitted redo log. Applying changes now... WARN org.apache.jackrabbit.core.query.lucene.MultiIndex 11.07.2005 14:23:23 -- Redo changes applied. after this, the search index is definitively out of sync and it need to be deleted... > 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
