You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2017/12/22 05:02:00 UTC
[jira] [Resolved] (JCR-2292) attempt to access a deleted document
[ https://issues.apache.org/jira/browse/JCR-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-2292.
---------------------------------
Resolution: Cannot Reproduce
> 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
> Components: query
> Affects Versions: 1.6
> 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 was sent by Atlassian JIRA
(v6.4.14#64029)