tree ade0445927885accb3eb77d54ff8bc829ea02d15
parent 29205e5490ef17c6b8bce3b9a9e0820461b3e964
author Saša Živkov <sasa.zivkov@sap.com> 1705655295 +0100
committer Saša Živkov <sasa.zivkov@sap.com> 1705657033 +0100

Fix heartbeat task leak after lock reclaim

Reclaiming an existing lock (re)started the heartbeat task but it missed
to set the heartbeatTask reference. After a reclaimed lock was closed
the heartbeat task wasn't stopped because the heartbeatTask reference
was null. The heartbeat thread continued to run on the scheduled rate
indefinitely.

Make sure to set the heartbeatTask reference after a lock is reclaimed.
Extend the tests to verify the heartbeat task is running/stopped.

Change-Id: Iecb7b77f54ad416a3a4de27bf26942270cfc3c1e