[MAGNOLIA-3261] Concurrent session changes are not visible when repository uses copy-on-read strategy Created: 02/Aug/10  Updated: 11/Jan/11  Resolved: 08/Oct/10

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.3.5
Fix Version/s: 4.4

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-3503 Session refresh should not assume ses... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

There are 2 ways how repo can deal with the sessions.

  • copy-on-read (eg. ModeShape) copies persisted state to transient and further changes will not be visible until refresh.
  • copy-on-write (eg. JackRabbit) copies data from persistent state only when they are to be changed and all other changes are visible without the refresh.

more on http://www.day.com/specs/jcr/1.0/7.1.3.4_Seeing_Changes_Made_by_Other_Sessions.html

One possible way to deal with the issue is to force refresh using observer in the repository strategy.


Generated at Mon Feb 12 03:44:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.