Concurrency basics · interview question
Why should locks acquired using ReentrantLock be released in a finally block?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencysynchronized-and-locks
Answer and explanation
Correct answer
B. To ensure that the thread does not hold the lock indefinitely.
Why
Releasing locks in a finally block ensures that locks are released even if an exception is thrown, preventing potential deadlocks and ensuring other threads can proceed.
Test yourself on Concurrency basics
A free test with instant, explained results. No account needed.
More Concurrency basics questions
- How can you avoid deadlocks when using multiple ReentrantLocks in a method?
- What does the 'volatile' keyword guarantee in Java?
- Why might using 'volatile' alone be insufficient for ensuring thread safety when updating a shared counter?
- Consider the following code snippet. What issue might occur if 'flag' is not declared as 'volatile'?
- When using synchronized blocks, how can you ensure fairness among threads?
- How would you explain a common use case for 'volatile' variables in an interview?