[OAK-2384] SegmentNotFoundException when keeping JCR Value references

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.0.12, 1.1.8
• Component/s: core
• Labels: gc
• Epic Link: SegmentMK revision GC
• Assignee: Michael Dürig
• Reporter: Michael Dürig
• Created: 09/Jan/15 11:21
• Updated: 16/Feb/21 09:53
• Resolved: 02/Mar/15 13:11

Description

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.

Issue Links

• is related to: OAK-2045 Long running JCR session prevent live cleanup in Segment FileStore