Is there an advantage to use a Synchronized Method instead of a Synchronized Block?

by

Can anyone tell me the advantage of the synchronized method over the synchronized block with an example? Thanks.

There is not a clear advantage of using synchronized method over the block.

Perhaps the only one ( but I wouldn’t call it an advantage ) is you don’t need to include the object reference this.

Method:

public synchronized void method() { // blocks "this" from here.... 
    ...
    ...
    ...
} // to here

Block:

public void method() { 
    synchronized( this ) { // blocks "this" from here .... 
        ....
        ....
        ....
    }  // to here...
}

See? No advantage at all.

Blocks do have advantages over methods though, mostly in flexibility because you can use another object as lock whereas syncing the method would lock the entire object.

Compare: 

// locks the whole object
... 
private synchronized void someInputRelatedWork() {
    ... 
}
private synchronized void someOutputRelatedWork() {
    ... 
}

vs. 

// Using specific locks
Object inputLock = new Object();
Object outputLock = new Object();

private void someInputRelatedWork() {
    synchronized(inputLock) { 
        ... 
    } 
}
private void someOutputRelatedWork() {
    synchronized(outputLock) { 
        ... 
    }
}

Also if the method grows you can still keep the synchronized section separated:

 private void method() {
     ... code here
     ... code here
     ... code here
    synchronized( lock ) { 
        ... very few lines of code here
    }
     ... code here
     ... code here
     ... code here
     ... code here
}

More Related Contents:

  1. Java synchronized method lock on object, or method?
  2. Java Synchronized Block for .class
  3. How to solve the “Double-Checked Locking is Broken” Declaration in Java?
  4. What is the difference between synchronized on lockObject and using this as the lock?
  5. Java : Does wait() release lock from synchronized block
  6. If a synchronized method calls another non-synchronized method, is there a lock on the non-synchronized method
  7. Avoid synchronized(this) in Java?
  8. How to wait for all threads to finish, using ExecutorService?
  9. Why is creating a Thread said to be expensive?
  10. Do spurious wakeups in Java actually happen?
  11. Java Wait and Notify: IllegalMonitorStateException
  12. Are static variables shared between threads?
  13. How do synchronized static methods work in Java and can I use it for loading Hibernate entities?
  14. Is iterating ConcurrentHashMap values thread safe?
  15. Happens-before relationships with volatile fields and synchronized blocks in Java – and their impact on non-volatile variables?
  16. Is it safe to get values from a java.util.HashMap from multiple threads (no modification)?
  17. Is ConcurrentHashMap totally safe?
  18. In Java critical sections, what should I synchronize on?
  19. Constructor synchronization in Java
  20. Javafx: Difference between javafx.concurent and Platform.runLater?
  21. Instruction reordering & happens-before relationship [duplicate]
  22. When should we use Java’s Thread over Executor?
  23. Java volatile modifier and synchronized blocks
  24. ThreadPoolExecutor Block When its Queue Is Full?
  25. Java Multithreading concept and join() method
  26. Difference between Synchronized block with wait/notify and without them?
  27. Concurrent JUnit testing
  28. Handling Exceptions for ThreadPoolExecutor
  29. notifyAll() throws IllegalMonitorStateException
  30. ExecutorCompletionService? Why do need one if we have invokeAll?

Leave a Comment