[MAGNOLIA-206] inconsistent config activation Created: 23/Nov/04  Updated: 23/Jan/13  Resolved: 24/Nov/04

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.0 Final
Fix Version/s: 2.01

Type: Bug Priority: Major
Reporter: Sameer Charles Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

all


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   

On recursive activation admin gui classes sends a request for the whole tree at one.
which results in out of memory while creating serializable objects.

fix:
change SimpleExchange Syndicator such that it splits the request in smaller chunks



 Comments   
Comment by Sameer Charles [ 23/Nov/04 ]

updated Tree.java such that it activates in chunks.
ll need a incremental activated implemented soon.

Comment by Sameer Charles [ 24/Nov/04 ]

tested on mac OSx and windows 2000 server, activation still takes long for a big tree
but quite stable

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