| Java FAQ | ||
| JSP FAQ | ||
| Servlet FAQ | ||
XyzWs Java FAQ:
What are differences between synchronized method and synchronized statement?
Printer-friendly version |
Mail this to a friend
|
Advertisement
|
What are differences between synchronized method and synchronized block (statement)?The synchronization is the capability to control the access of multiple threads to shared resources. Without synchronization, it is possible for one thread to modify a shared resource while another thread is in the process of using or updating that resource. There two synchronization syntax in Java Language. The practical differences are in controlling scope and the monitor. With a synchronized method, the lock is obtained for the duration of the entire method. With synchronized blocks you can specify exactly when the lock is needed. Basically, synchronized blocks are more general, and synchronized methods can be rewritten to use synchronized blocks:
class Program {
public synchronized void f() {
.........
}
}
is equivalent to
class Program {
public void f() {
synchronized(this){
...
}
}
}
For example, You have a method with some parts that need synchronized and others don't. The synchronized block lets you synchronize only the partial line codes that really need it.
public class Program {
private static Object locker1 = new Object();
private static Object locker1 = new Object();
public void doSomething1() {
...
synchronized(locker1) {
......... //do something protected;
}
....
}
public void doSomething2() {
...
synchronized(locker2) {
......... //do something protected;
}
....
}
}
The synchronized block can only be executed after a thread has acquired the lock for the object or class referenced, for example the "locker1" or "locker2" in above code, in the synchronized statement.
The above code shows that synchronized block can be holding different object
monitors. Maybe it's necessary to protect A synchronized method synchronizes on the object instance or the class. A thread only executes a synchronized method after it has acquired the lock for the method's object or class.
These are very public monitors, meaning some other thread could synchronize on them for the wrong reason, leading to slowdowns or deadlocks.
|