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

Improve multithreading support for transactional activation

XMLWordPrintable

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

      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.

        Acceptance criteria

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

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD