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

Avoid possible concurrency on jcr session in LockManager and do not proceed with lock refreshing if timeout cannot be set due to repository exception

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 5.0.0
    • None
    • None
    • Turing Sprint 155, Turing Sprint 156

    Attachments

      Issue Links

        is cloned by

        Bug - A problem which impairs or prevents the functions of the product. REPO-1671 [Backport 4.2] Avoid possible concurrency on jcr session in LockManager and do not proceed with lock refreshing if timeout cannot be set due to repository exception

        • Normal - Normal priority, tasks to be done before next intermediate release
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. REPO-1672 [Backport 4.1] Avoid possible concurrency on jcr session in LockManager and do not proceed with lock refreshing if timeout cannot be set due to repository exception

        • Normal - Normal priority, tasks to be done before next intermediate release
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. REPO-1673 [Backport 3.2.8] Avoid possible concurrency on jcr session in LockManager and do not proceed with lock refreshing if timeout cannot be set due to repository exception

        • Normal - Normal priority, tasks to be done before next intermediate release
        • Closed

        Activity

          People

            Unassigned Unassigned
            aschrijvers Ard Schrijvers
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: