xadisk
  1. xadisk
  2. XADISK-86

If LockTimeOut is set to 0, the request to acquire a lock may endup in a loop until the lock is acquired.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1
    • Fix Version/s: 1.2
    • Component/s: filesystem
    • Labels:
      None

      Description

      If the configuration property "LockTimeOut" is set to 0, during an operation which requires locking a file/dir, the thread will keep rotating in a loop until the lock by the existing holder is released. It is expected that the wait should happen without consuming unnecessary cpu cycles.

      The underlying cause is due to our replacing of the Object.wait(time) method with the recommended Condition.await(time) method. The former method waits indefinitely if time argument is 0, but (we missed this unfortunately) the later does not.

        Activity

        Hide
        Nitin Verma added a comment -

        Checked-in the changes to trunk.

        Show
        Nitin Verma added a comment - Checked-in the changes to trunk.

          People

          • Assignee:
            Nitin Verma
            Reporter:
            Nitin Verma
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: