[MGNLXAA-19] Improve multithreading support for transactional activation Created: 26/Jun/09  Updated: 04/Oct/13  Resolved: 02/Jul/09

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.0.2
Fix Version/s: 1.0.5, 1.1.2

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

Issue Links:
Cloners
dependency
depends upon MAGNOLIA-2807 Make ActivationContent clonable 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
Date of First Response:

 Description   

Currently all activation threads share same instance of activation content. This can lead to issues when different subscribers try to activate content in different parent path if they are executed in very short time window apart (the paths get mixed). The solution to the issue is to ensure each of the activation threads uses its own copy of the ActivationContent.



 Comments   
Comment by Jan Haderka [ 02/Jul/09 ]

Done as of r26581.

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