1. 同步与死锁
1.1 同步
说到线程,同步是一个不得不说的话题,为什么呢?因为多个线程访问同一资源时,如果不进行同步处理,那就会出问题。大家喜闻乐见的当然是卖票问题,如:
//源码:
public class ThreadByImplements_201810302136 implements Runnable{
private int mTicket = 5;
@Override
public void run() {
for (int i = 0; i < 25; i++) {
if(mTicket > 0){
try {
Thread.sleep(100);
} catch (InterruptedException e) {
e.printStackTrace();
}
System.out.println(Thread.currentThread().getName() + " " + (mTicket--));
}
}
}
public static void main(String[] args) {
ThreadByImplements_201810302136 r1 = new ThreadByImplements_201810302136();
Thread t1 = new Thread(r1,"THREAD-A-天王盖地虎");
Thread t2 = new Thread(r1,"THREAD-B-宝塔镇河妖");
Thread t3 = new Thread(r1,"THREAD-C-小鸡炖蘑菇");
t1.start();
t2.start();
t3.start();
}
}
//执行结果:
THREAD-A-天王盖地虎 3
THREAD-C-小鸡炖蘑菇 5
THREAD-B-宝塔镇河妖 4
THREAD-B-宝塔镇河妖 2
THREAD-A-天王盖地虎 2
THREAD-C-小鸡炖蘑菇 1
THREAD-B-宝塔镇河妖 0
THREAD-A-天王盖地虎 -1
其实简单分析一下就能明白为什么会出现上面的执行结果。在线程主体中,判断票数是否大于零,如果票数大于零,则卖,反之,则不卖。这样就会出现一种情况:票数为 1 的时候,一个线程刚把票买走,系统还没有来得及减,另外一个线程又进来了,由于系统此时还没有来得及减,所以此时票数还是大于零,结果后来的线程也买到票了。
要解决上面的问题,必须使用同步。所谓同步是指在同一时间段内,只能有一个线程对数据进行操作,其他线程只能等这个线程操作完之后才可以操作。
线程同步的方法有两种:同步代码块和同步方法。接下来,分别用两种方式对上面的例子进行处理。
1.1.1 同步代码块
1.1.1.1 语法
synchronized (同步对象) {
//需要同步的代码块
}
1.1.1.2 实例
//源码:
public class ThreadByImplements_201810302208 implements Runnable {
private int mTicket = 5;
@Override
public void run() {
for (int i = 0; i < 25; i++) {
synchronized (this) {
if(mTicket > 0){
try {
Thread.sleep(100);
} catch (InterruptedException e) {
e.printStackTrace();
}
System.out.println(Thread.currentThread().getName() + " " + (mTicket--));
}
}
}
}
public static void main(String[] args) {
ThreadByImplements_201810302208 r1 = new ThreadByImplements_201810302208();
Thread t1 = new Thread(r1,"THREAD-A-天王盖地虎");
Thread t2 = new Thread(r1,"THREAD-B-宝塔镇河妖");
Thread t3 = new Thread(r1,"THREAD-C-小鸡炖蘑菇");
t1.start();
t2.start();
t3.start();
}
}
//执行结果:
THREAD-A-天王盖地虎 5
THREAD-A-天王盖地虎 4
THREAD-A-天王盖地虎 3
THREAD-A-天王盖地虎 2
THREAD-A-天王盖地虎 1
1.1.2 同步方法
1.1.2.1 语法
synchronized 方法返回值 方法名(参数列表){}
1.1.2.2 实例
//源码:
public class ThreadByImplements_201810302220 implements Runnable {
private int mTicket = 5;
@Override
public void run() {
for (int i = 0; i < 25; i++) {
saleTicket();
}
}
private synchronized void saleTicket(){
if(mTicket > 0){
try {
Thread.sleep(100);
} catch (InterruptedException e) {
e.printStackTrace();
}
System.out.println(Thread.currentThread().getName() + " " + (mTicket--));
}
}
public static void main(String[] args) {
ThreadByImplements_201810302220 r1 = new ThreadByImplements_201810302220();
Thread t1 = new Thread(r1,"THREAD-A-天王盖地虎");
Thread t2 = new Thread(r1,"THREAD-B-宝塔镇河妖");
Thread t3 = new Thread(r1,"THREAD-C-小鸡炖蘑菇");
t1.start();
t2.start();
t3.start();
}
}
//执行结果:
THREAD-A-天王盖地虎 5
THREAD-A-天王盖地虎 4
THREAD-A-天王盖地虎 3
THREAD-A-天王盖地虎 2
THREAD-A-天王盖地虎 1
1.2 死锁
同步解决了资源共享时数据错乱的问题,但并不代表同步处理越多越好。例如,周五的时候,你和女票在家做了一顿饭。吃完饭,女票让你刷锅,你让女票打扫卫生。小仙女可不想打扫卫生,于是说:“等你刷完锅,我就开始打扫卫生”。你一眼识破了女票诡计,于是也说了句:“等你扫完地,我就开始刷锅”。就这样,到了第二天,你们的锅还没有刷,卫生还没有打扫,这实际上就是死锁的概念。
所谓死锁是指两个线程在等待对方先执行完,造成了程序的停滞。接下来就根据上面例子的示范一下,死锁是如何出现的:
//源码:
public class ThreadByImplements_201810302344 implements Runnable {
//由于是两个 Runnable 对象,所以必须使用静态成员变量才能实现资源共享
private static GirlFriend gf = new GirlFriend();
private static BoyFriend bf = new BoyFriend();
private boolean speakFirst = false;
@Override
public void run() {
if(speakFirst){
synchronized (gf) {
//1.先下手为强
gf.say();
try {
//2.等待对方刷碗
Thread.sleep(500);
} catch (InterruptedException e) {
e.printStackTrace();
}
synchronized (bf) {
//3.对方刷完碗,自己开始打扫卫生
gf.clean();
}
}
}else{
synchronized (bf) {
//a.以其人之道,还治其人之身
bf.say();
try {
//b.等待对方打扫卫生
Thread.sleep(500);
} catch (InterruptedException e) {
e.printStackTrace();
}
synchronized (gf) {
//c.对方打扫完卫生,自己开始刷锅
bf.wash();
}
}
}
}
public static void main(String[] args) {
ThreadByImplements_201810302344 gfRunnable = new ThreadByImplements_201810302344();
ThreadByImplements_201810302344 bfRunnable = new ThreadByImplements_201810302344();
gfRunnable.speakFirst = true;
bfRunnable.speakFirst = false;