如果某个线程视图获得一个已经由它自己持有的锁,那么这个请求就会成功。
public class Father {
protected synchronized void say() {
System.out.println(Thread.currentThread().getName() + " :father say!");
}
}
public class Child extends Father {
public synchronized void say() {
super.say();
System.out.println(Thread.currentThread().getName() + ": child say!");
}
public synchronized void sing() {
System.out.println(Thread.currentThread().getName() + ": child sing!");
for(;;){}
}
}
public class SynchronizedTest {
public static void main(String[] args) {
final Child child = new Child();
new Thread(new Runnable() {
@Override
public void run() {
child.say();
child.sing();
}
}).start();
new Thread(new Runnable() {
@Override
public void run() {
child.say();
child.sing();
}
}).start();
}
}
输出
Thread-0 :father say!
Thread-0: child say!
Thread-0: child sing!
可以看到,Thread-0可以访问当前线程其它(包括父类)锁方法,但由于Child 类的sing方法出现死锁,导致Thread-1处于等待状态。
线程dump如下
再来看看,对Child和Father的锁对象。
public class Father {
protected synchronized void say() {
System.out.println(Thread.currentThread().getName() + " :father say!");
for(;;){}
}
}
在Father类添加for(;;){}后,可以看到,Father 中say方法的锁对象是Child的实例。