jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (OAK-2384) SegmentNotFoundException when keeping JCR Value references
Date Mon, 02 Mar 2015 13:12:04 GMT

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

Michael Dürig resolved OAK-2384.
       Resolution: Fixed
    Fix Version/s:     (was: 1.0.13)

Fixed in trunk at http://svn.apache.org/r1663288
Fixed in 1.0 branch at http://svn.apache.org/r1663296

> 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
>              Labels: gc
>             Fix For: 1.0.12, 1.1.8
>         Attachments: org.apache.sling.jcr.resource-2.4.0.jar
> 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

View raw message