[
https://issues.apache.org/jira/browse/JCR-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763878#action_12763878
]
Marcel Reutegger commented on JCR-2292:
---------------------------------------
Can you please add the following parameters to the SearchIndex element in the
workspace.xml of the affected workspace and monitor the log file for
consistency check messages?
<param name="enableConsistencyCheck" value="true"/>
<param name="forceConsistencyCheck" value="true"/>
It'd be interesting to know what kind of nodes cause the issue. If possible try
to resolve the path from the given UUID in the log file using
Session.getNodeByUUID(<uuid>).getPath().
> attempt to access a deleted document
> ------------------------------------
>
> Key: JCR-2292
> URL: https://issues.apache.org/jira/browse/JCR-2292
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Affects Versions: 1.6.0
> Environment: Windows XP, Java 1.6.0_13-b03
> Reporter: Imran
> Priority: Critical
>
> When I run the query : items//*[(jcr:contains(@MYATTRIB, 'MYATTRIB-VALUE') I
> get results back.
> But if I add a "not" condition: items//*[not(jcr:contains(@MYATTRIB,
> 'MYATTRIB-VALUE') , I get "java.lang.IllegalArgumentException: attempt to
> access a deleted document" exception
> After I renamed the index directory [effectively forcing a re-index], and ran
> the application again, the "not" condition query works. If I restore the
> previous index I get the error again.
> The workaround of deleting index is fine in the development environment. But
> once we go to production, we will not have the option to delete the index
> directories.
> Btw, I found that a similar defect [JCR-1573] was reported and marked as
> fixed. Apparently it keeps re-surfacing under different conditions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
