【121期】面试官问：线程池执行过程中遇到异常会发生什么，如何处理？

jiameih

于 2024-05-01 00:06:27 发布

阅读量434

点赞数 15

分类专栏：程序员文章标签： python 开发语言

本文链接：https://blog.csdn.net/jiameih/article/details/138360216

版权

程序员专栏收录该内容

187 篇文章 0 订阅

订阅专栏

Exception in thread “customThread 5” java.lang.ArithmeticException: / by zero

at thread.ThreadExecutor.lambda$null$0(ThreadExecutor.java:25)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:748)

可见每次执行的线程都不一样，之前的线程都没有复用。原因是因为出现了未捕获的异常。面试题：公众号Java精选，回复Java面试，获取近3000道面试题，支持在线随时随地刷题。

我们把异常捕获试试：

public class ThreadExecutor {

private ThreadPoolExecutor threadPoolExecutor = new ThreadPoolExecutor(1, 1, 60, TimeUnit.SECONDS,

new ArrayBlockingQueue<>(200), new ThreadFactoryBuilder().setNameFormat(“customThread %d”).build());

@Test

public void test() {

IntStream.rangeClosed(1, 5).forEach(i -> {

try {

Thread.sleep(100);

} catch (InterruptedException e) {

e.printStackTrace();

}

threadPoolExecutor.execute(() -> {

try {

int j = 1 / 0;

} catch (Exception e) {

System.out.println(Thread.currentThread().getName() +" "+ e.getMessage());

}

});

}

customThread 0 / by zero

可见当异常捕获了，线程就可以复用了。

问题来了，我们的代码中异常不可能全部捕获

如果要捕获那些没被业务代码捕获的异常，可以设置Thread类的uncaughtExceptionHandler属性。这时使用ThreadFactoryBuilder会比较方便，ThreadFactoryBuilder是guava提供的ThreadFactory生成器。

new ThreadFactoryBuilder()

.setNameFormat(“customThread %d”)

.setUncaughtExceptionHandler((t, e) -> System.out.println(t.getName() + “发生异常” + e.getCause()))

.build()

修改之后：

public class ThreadExecutor {

private static ThreadPoolExecutor threadPoolExecutor = new ThreadPoolExecutor(1, 1, 60, TimeUnit.SECONDS,

new ArrayBlockingQueue<>(200),

new ThreadFactoryBuilder()

.setNameFormat(“customThread %d”)

.setUncaughtExceptionHandler((t, e) -> System.out.println(“UncaughtExceptionHandler捕获到：” + t.getName() + “发生异常” + e.getMessage()))

.build());

@Test

public void test() {

IntStream.rangeClosed(1, 5).forEach(i -> {

try {

Thread.sleep(100);

} catch (InterruptedException e) {

e.printStackTrace();

}

threadPoolExecutor.execute(() -> {

System.out.println(“线程” + Thread.currentThread().getName() + “执行”);

int j = 1 / 0;

});

}

线程customThread 0执行

UncaughtExceptionHandler捕获到：customThread 0发生异常/ by zero

线程customThread 1执行

UncaughtExceptionHandler捕获到：customThread 1发生异常/ by zero

线程customThread 2执行

UncaughtExceptionHandler捕获到：customThread 2发生异常/ by zero

线程customThread 3执行

UncaughtExceptionHandler捕获到：customThread 3发生异常/ by zero

线程customThread 4执行

UncaughtExceptionHandler捕获到：customThread 4发生异常/ by zero

可见，结果并不是我们想象的那样，线程池中原有的线程没有复用！所以通过UncaughtExceptionHandler想将异常吞掉使线程复用这招貌似行不通。它只是做了一层异常的保底处理。

将excute改成submit试试

public class ThreadExecutor {

private static ThreadPoolExecutor threadPoolExecutor = new ThreadPoolExecutor(1, 1, 60, TimeUnit.SECONDS,

new ArrayBlockingQueue<>(200),

new ThreadFactoryBuilder()

.setNameFormat(“customThread %d”)

.setUncaughtExceptionHandler((t, e) -> System.out.println(“UncaughtExceptionHandler捕获到：” + t.getName() + “发生异常” + e.getMessage()))

.build());

@Test

public void test() {

IntStream.rangeClosed(1, 5).forEach(i -> {

try {

Thread.sleep(100);

} catch (InterruptedException e) {

e.printStackTrace();

}

Future<?> future = threadPoolExecutor.submit(() -> {

System.out.println(“线程” + Thread.currentThread().getName() + “执行”);

int j = 1 / 0;

});

try {

future.get();

} catch (InterruptedException e) {

e.printStackTrace();

} catch (ExecutionException e) {

e.printStackTrace();

}

});

}

线程customThread 0执行