Jackrabbit Content Repository
  1. Jackrabbit Content Repository
  2. JCR-2290

Potential concurrency issues of Workspace operations

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: jackrabbit-core
    • Labels:
      None

      Description

      while investigating JCR-2269 i discovered that the following javax.jcr.Workspace operations are affected by potential concurency issues:

      copy
      clone
      move
      importXML
      getImportContentHandler

      those operations directly operate on ItemState instances returned from LocalItemStateManager (LISM).
      typically a workspace operation gets an ItemState instance from the LISM, does some validations,
      modifies the state and finally stores it in the ChangeLog for further processing.

      the problem is that the local ItemState instance is not isolated from external changes, i.e. it might change
      at any point (e.g. after validation) due to external underlying changes. only when it is stored in the
      ChangeLog it is disconnected from its underlying state.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Stefan Guggisberg
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development