Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-5385

Make Autogeneration thread/clustering safe

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 5.1.1
    • 4.5
    • templating
    • None

      When opening page w/ autogenerated component for the first time, template renderer will trigger autogeneration. If there are multiple requests for display of the same page, one will fail with InvalidItemStateException or with ItemNotFoundException depending in which phase of autogeneration error occurs.
      Existing code attempts to work around the issue by hiding the exception and waiting for up to half second for autogenerated node to become visible. While this diminishes possibility of reaching race condition, it still exists and should be avoided.

      Solution used here should outline the way for general mechanism to handle concurrent editing once full author clustering is supported.

        Acceptance criteria

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

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD