-
Bug
-
Resolution: Done
-
Medium
-
Amsterdam Release, Beijing Release, Casablanca Release, Dublin Release
-
None
The resource locking in RA behaves incorrectly, when there is an expired lock record in DB. In such case, although the lock is granted, the same record is used and updated to not be expired. However, the lock_holder is not updated based on the new lock_requester and the lock_count is incremented. This leads to the updated not expired record remaining in DB after the lock is released by the client.