Threads – Why a Lock has to be followed by try and finally

by

Because a try/finally block is the only way to guarantee that a segment of code is executed after another completes.

You ask why not do this:

public void function1(){
    read.lock();
    this.getSharedInt();
    read.unlock();
}

What happens when this.getSharedInt() throws an exception? Then your read.unlock() line will not be executed, causing program deadlock. Sure, it may be 100% certified to not throw an exception right now, but what happens when you refactor to store that shared int in a file or database?

Finally, don’t forget that try/finally also accounts for errors, which can be thrown by the runtime at almost any line in a program, even if the function is guaranteed to not throw any exceptions.

Note that this code would also work, but it swallows the exception. Using finally instead allows the exception to propagate normally, while still unlocking under all conditions.

public void function2(){
    read.lock();
    try {
        this.getSharedInt();
    } catch(Throwable t) {}
    read.unlock();
}

More Related Contents:

  1. Java synchronized method lock on object, or method?
  2. Why is volatile used in double checked locking
  3. Is there an advantage to use a Synchronized Method instead of a Synchronized Block?
  4. Why is Java’s SimpleDateFormat not thread-safe? [duplicate]
  5. Do spurious wakeups in Java actually happen?
  6. Is java.sql.Connection thread safe?
  7. Is iterating ConcurrentHashMap values thread safe?
  8. Is HttpSession thread safe, are set/get Attribute thread safe operations?
  9. Is RestTemplate thread safe?
  10. Why are local variables thread safe in Java
  11. Java Synchronized Block for .class
  12. How to solve the “Double-Checked Locking is Broken” Declaration in Java?
  13. Must Spring component classes be thread-safe
  14. Should we use EventQueue.invokeLater for any GUI update in a Java desktop application?
  15. Which Swing component methods are thread safe?
  16. Distributed Lock Service [closed]
  17. Java Concurrency: CAS vs Locking [closed]
  18. What is thread Safe in java? [duplicate]
  19. Throttling javafx gui updates
  20. Are primitive datatypes thread-safe in Java
  21. Odd even number printing using thread
  22. Java : Does wait() release lock from synchronized block
  23. How to implement thread-safe lazy initialization?
  24. How to acquire a lock by a key
  25. final fields and thread-safety
  26. Java Synchronization [closed]
  27. Is Cipher thread-safe?
  28. Are arrays thread-safe in Java?
  29. Constructors and instruction reordering
  30. ReentrantReadWriteLock: what’s the difference between ReadLock and WriteLock?

Leave a Comment