Uploaded image for project: 'Transactional Activation'
  1. Transactional Activation
  2. MGNLXAA-19

Improve multithreading support for transactional activation

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 1.0.5, 1.1.2
    • 1.0.2
    • None

    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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                had Jan Haderka
                zdenekskodik Zdenek Skodik
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD