Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-777

Race conditions in cleaning up stale locks held by dead members in a cluster

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Out of Date
    • Affects Version/s: 4.2.0.BETA1
    • Fix Version/s: 5.3.0.Final
    • Component/s: Transactions
    • Labels:
      None

      Description

      It seems that rollback sometimes does not release acquired eager locks. See attached test program and run two JVM instances on the same machine. Program schedules a task to run every 5 seconds. Tasks simply locks a key, gets the value, increases the value and puts it back surrounded by begin/commit/rollback tx boundary.

      Steps to reproduce (keep repeating steps until problem is encountered):

      1) Kill one running instance.
      2) Restart it

      See attached example output of a run.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mircea.markus Mircea Markus
                  Reporter:
                  vblagojevic Vladimir Blagojevic
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: