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

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

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • 5.3.0.Final
    • 4.2.0.BETA1
    • Transactions
    • None

      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.

        1. CacheScheduledCounter.java
          6 kB
          Vladimir Blagojevic
        2. ISPN-777_output.txt
          4 kB
          Vladimir Blagojevic

              mircea.markus Mircea Markus (Inactive)
              vblagoje Vladimir Blagojevic (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: