[
https://issues.apache.org/jira/browse/JCR-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214636#comment-13214636
]
Ravish Bhagdev edited comment on JCR-2427 at 2/23/12 4:34 PM:
--------------------------------------------------------------
We just faced this issue with Magnolia CMS running on Jackrabbit 1.6.4. We ran
consistency check on the affected repository and restarted Jackrabbit.
Consistency check found a bunch of errors it could not fix (orphaned nodes
mainly but nothing else obvious was reported). The exception has disappeared
since.
Is there any way to reproduce this? We have seen this before, so need to
understand when/how it happens so we can decide a way to proceed.
was (Author: ravish):
We just faced this issue with Magnolia CMS running on Jackrabbit 1.6.4. We
ran consistency check on the affected repository and restarted Jackrabbit. The
exception has disappeared since.
Is there any way to reproduce this? We have seen this before, so need to
understand when/how it happens so we can decide a way to proceed.
> UUIDDocId.getDocumentNumbers() may return illegal value
> -------------------------------------------------------
>
> Key: JCR-2427
> URL: https://issues.apache.org/jira/browse/JCR-2427
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.0-beta5
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.6.5, 2.0-beta6
>
>
> Happens when the node with the given UUID is not present in the index. The
> method then returns -1, which is illegal. Document numbers must be >= 0. The
> method must returns an empty array when the id is invalid, as documented in
> DocId.getDocumentNumbers().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
