[MAGNOLIA-4450] Force session refresh after auto-creation of areas Created: 20/Jun/12  Updated: 17/Dec/14  Resolved: 20/Jun/12

Status: Closed
Project: Magnolia
Component/s: integration tests
Affects Version/s: 4.5.3
Fix Version/s: 4.5.4

Type: Task Priority: Neutral
Reporter: Daniel Lipp Assignee: Jan Haderka
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-4462 Force session refresh after auto-crea... Closed
relation
is related to MAGNOLIA-5009 PathNotFoundException on newly create... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

In certain cases areas need to be auto created when rendering pages. In order to ensure smooth creation, it is done in system context. If server is under heavy load, refresh of the user session that depends on area to exist will not see it fast enough.



 Comments   
Comment by Jan Haderka [ 27/Jun/12 ]

what it seems like at the moment is that area node is auto created successfully ( no "ignoring problem w/ creating area in workspace ..." error message), but it is not visible to the normal node (previously retrieved), hence the "Can't access area node [metaNavigation] on ..." message. This could be either because of the wrapper bug or due to slowness of refresh of the node in session (but under different privileges).

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