[MAGNOLIA-3503] Session refresh should not assume sessions are thread safe Created: 11/Jan/11  Updated: 19/Jan/11  Resolved: 19/Jan/11

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.4.1
Fix Version/s: 4.4.2

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

Issue Links:
causality
caused by MAGNOLIA-3261 Concurrent session changes are not vi... Closed
supersession
supersedes MGNLMSHAPE-11 Provide hierarchy manager with automa... 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   

Forced session refresh introduced by MAGNOLIA-3261, introduces access to sessions from different threads and assumes sessions are thread safe. However JCR specification makes no such requirement. The refresh should be instead performed only on demand (i.e. when session encounters ItemNotFoundException ).



 Comments   
Comment by Jan Haderka [ 18/Jan/11 ]

Move the refresh into MS module for now in custom implementation of HierarchyManager.

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