[ http://issues.apache.org/jira/browse/JCR-160?page=comments#action_12315710 ]
Marcel Reutegger commented on JCR-160: -------------------------------------- Improved query handler: - A possible commit.lock is now also removed on startup. Previously only a write.lock was removed. - An integrity check is run if the search index detects a commit or write lock on startup. This check removes nodes from the index that are not available anymore through the ItemStateManager. - Applying the redo log on startup is now more failsafe. svn revision: 216142 > 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
