[MGNLXAA-17] Activation ends with OOM when activation deeply nested content Created: 16/Apr/09  Updated: 04/Oct/13  Resolved: 17/Apr/09

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.0.2, 1.1
Fix Version/s: 1.0.3, 1.1.1

Type: Bug Priority: Critical
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:
relation
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   

Due to limitations of workspace cloning, creating of temporary copy of content (for possible rollback) in XA transaction might consume all available system resources and end up with OOM.
This issue is somewhat less critical when using Java 6 and JR 1.5.3, but still present.
Since the workspace cloning op doesn't support filtering of the content, solution to this issue is to recursively copy the node in question and all it's subnodes and use cloning only for leaves of such subtree.



 Comments   
Comment by Jan Haderka [ 17/Apr/09 ]

Done on trunk as of r24384 and on 1.0 branch (Mgnl 3.6 compat) as of r24411.

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