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

Activation ends with OOM when activation deeply nested content

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 1.0.3, 1.1.1
    • 1.0.2, 1.1
    • None

    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.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              had Jan Haderka
              had Jan Haderka
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD