Uploaded image for project: '[Read Only] - Hippo Repository'
  1. [Read Only] - Hippo Repository
  2. REPO-1192

Lock timeout in initialization processor is not reliable

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.26.11, 2.28.00
    • Component/s: None
    • Labels:
    • Similar issues:

      Description

      Content bootstrap can interfere with the lock timeout. See attached stacktrace.

      What happens is that the Jackrabbit LockManager implementation unlocks timed out locks on a separate thread while using the same underlying session that is currently being used for bootstrapping, i.e. it contains a concurrent session access bug. So when the lock is timed out and the bootstrap process is still in progress we get concurrent modification exceptions due to this concurrent session access. Until this is resolved in Jackrabbit we are better off avoiding the lock time-out mechanism together with a write-intensive process such as bootstrapping.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jsheriff Junaidh Kadhar Sheriff
                Reporter:
                abanck Arent-Jan Banck
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: