You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/01/09 12:22:35 UTC

[jira] [Updated] (OAK-2384) SegmentNotFoundException when keeping JCR Value references

     [ https://issues.apache.org/jira/browse/OAK-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig updated OAK-2384:
-------------------------------
    Priority: Critical  (was: Major)

> SegmentNotFoundException when keeping JCR Value references
> ----------------------------------------------------------
>
>                 Key: OAK-2384
>                 URL: https://issues.apache.org/jira/browse/OAK-2384
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Critical
>             Fix For: 1.0.10, 1.1.5
>
>
> With OAK-2192 revision gc started to remove segments older than a certain threshold. The underlying assumption was that old sessions would call refresh (i.e. auto refresh) anyway once they become active again. However, it turns out that refreshing a sessions does not affect JCR values as those are directly tied to the underlying record. Accessing those values after its segment has been gc'ed results in a {{SegmentNotFoundException}}. 
> Keeping reference to JCR values is an important use case for Sling's {{JcrPropertyMap}}, which is widely used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)