gpt4 book ai didi

java - 理解java中的死锁

转载 作者:行者123 更新时间:2023-12-01 17:24:55 25 4
gpt4 key购买 nike

下面给出的是我发现的关于死锁的示例并且它有效。我的问题是currentThread()如何工作?而且 A 和 B 并不是专门作为线程创建的,即:

Deadlock d=new Deadlock();
Thread A=new Thread(d)

代码如何仍然有效?

class A {
synchronized void foo(B b) {
String name = Thread.currentThread().getName();
System.out.println(name + " entered A.foo");
try {
Thread.sleep(1000);
} catch (Exception e) {System.out.println("A Interrupted");
}
System.out.println(name + " trying to call B.last()");
b.last();
}

synchronized void last() {
System.out.println("Inside A.last");
}
}

class B {
synchronized void bar(A a) {
String name = Thread.currentThread().getName();
System.out.println(name + " entered B.bar");
try {
Thread.sleep(1000);
} catch (Exception e) {System.out.println("B Interrupted");
}
System.out.println(name + " trying to call A.last()");
a.last();
}
synchronized void last() {
System.out.println("Inside A.last");
}
}

public class Deadlock implements Runnable {
A a = new A();
B b = new B();

Deadlock() {
Thread.currentThread().setName("MainThread");
Thread t = new Thread(this, "RacingThread");
t.start();
a.foo(b); // get lock on a in this thread.
System.out.println("Back in main thread");
}

public void run() {
b.bar(a); // get lock on b in other thread.
System.out.println("Back in other thread");
}

public static void main(String args[]) {
new Deadlock();
}
}

最佳答案

我认为这是一个相当令人困惑的死锁示例 - 它增加了问题的其他噪音。

可以通过使用 Lock 对象来实现一个非常简单的示例,如下所示:

public class App {

private static final Lock LOCKA = new ReentrantLock();
private static final Lock LOCKB = new ReentrantLock();

private static final class Locker1 implements Runnable {

@Override
public void run() {
while (true) {
try {
LOCKA.lockInterruptibly();
Thread.sleep(100);
LOCKB.lockInterruptibly();
System.out.println("Locker 1 Got locks");
} catch (InterruptedException ex) {
return;
}
LOCKB.unlock();
LOCKA.unlock();
}
}
}

private static final class Locker2 implements Runnable {

@Override
public void run() {
while (true) {
try {
LOCKB.lockInterruptibly();
Thread.sleep(100);
LOCKA.lockInterruptibly();
System.out.println("Locker 2 Got locks");
} catch (InterruptedException ex) {
return;
} finally {
LOCKA.unlock();
LOCKB.unlock();
}
}
}
}

public static void main(String[] args) throws IOException {
final ExecutorService executorService = Executors.newFixedThreadPool(2);
executorService.submit(new Locker1());
executorService.submit(new Locker2());

}
}

应用程序在执行器中启动两个线程,然后我们让这些线程调用两个可运行对象。

这些可运行对象尝试以相反的顺序获取两个 Lock 对象的锁。

因此,Locker1 锁定 LOCKA,然后等待几毫秒。 Locker2 锁定 LOCKB 并等待几毫秒,然后尝试获取另一个锁。

情况是,Locker1 等待 LOCKB,而 Locker2 与其他线程一样永远等待 LOCKA永远不会释放它。

您可以在这些线程的线程转储中清楚地看到这一点:

"pool-1-thread-1" - Thread t@8
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Native Method)
- waiting to lock <7725204d> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) owned by "pool-1-thread-2" t@9
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireInterruptibly(AbstractQueuedSynchronizer.java:894)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1221)
at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:340)
at com.boris.testbench.App$Locker1.run(App.java:32)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)

Locked ownable synchronizers:
- locked <7567e1fa> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)

- locked <5ad52411> (a java.util.concurrent.ThreadPoolExecutor$Worker)

"pool-1-thread-2" - Thread t@9
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Native Method)
- waiting to lock <7567e1fa> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) owned by "pool-1-thread-1" t@8
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireInterruptibly(AbstractQueuedSynchronizer.java:894)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1221)
at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:340)
at com.boris.testbench.App$Locker2.run(App.java:51)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)

Locked ownable synchronizers:
- locked <7725204d> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)

- locked <6856c528> (a java.util.concurrent.ThreadPoolExecutor$Worker)

我们可以看到pool-1-thread-1想要锁定pool-1-thread-2pool-1拥有的锁-thread-2想要锁定pool-1-thread-1拥有的锁。

这种情况将永远持续下去,因此陷入僵局。

您的代码实现了相同的结果,但不是使用手动生成的两个线程,而是使用应用程序主线程(由 JVM 生成)和手动生成的一个线程。

它还在两个 Object 中使用synchronized 方法,而不是两个 Lock 对象。

关于java - 理解java中的死锁,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/15745329/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com