SpringBoot—自定义线程池及并发定时任务模板
介绍
在项目开发中,经常遇到定时任务,今天通过自定义多线程池总结一下SpringBoot默认实现的定时任务机制。
定时任务模板
pom依赖
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
//线程池用到
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>22.0</version>
</dependency>
//@Slf4j注解用到
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<optional>true</optional>
<version>1.18.4</version>
</dependency>
</dependencies>
自定义线程池模板
package com.example.andya.demo.conf;
import com.google.common.util.concurrent.ThreadFactoryBuilder;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import java.util.concurrent.*;
/**
* @author Andya
* @create 2020-05-29 14:08
*/
@Configuration
public class ThreadPoolConfig {
public static String THREAD_NAME = "first-thread-pool-%d";
public static final int CORE_POOL_SIZE = Runtime.getRuntime().availableProcessors() * 2 + 1;
public static int MAX_POOL_SIZE = 10;
public static int QUEUE_SIZE = 10;
/**
* 自定义消费队列线程池
*
* @return
*/
@Bean(value = "firstThreadPool")
public ExecutorService buildFirstThreadPool() {
ThreadFactory threadFactory = new ThreadFactoryBuilder().setNameFormat(THREAD_NAME).build();
/**
* 1. CallerRunsPolicy : 这个策略重试添加当前的任务,他会自动重复调用 execute() 方法,直到成功。
2. AbortPolicy : 对拒绝任务抛弃处理,并且抛出异常。
3. DiscardPolicy : 对拒绝任务直接无声抛弃,没有异常信息。
4. DiscardOldestPolicy : 对拒绝任务不抛弃,而是抛弃队列里面等待最久的一个线程,然后把拒绝任务加到队列。
*/
ExecutorService threadPool = new ThreadPoolExecutor(
CORE_POOL_SIZE,
MAX_POOL_SIZE,
0L,
TimeUnit.SECONDS,
new LinkedBlockingQueue<>(QUEUE_SIZE),
threadFactory,
new ThreadPoolExecutor.AbortPolicy());
return threadPool;
}
}
定时任务模板
package com.example.andya.demo.service;
import lombok.extern.slf4j.Slf4j;
import org.springframework.scheduling.annotation.EnableScheduling;
import org.springframework.scheduling.annotation.Scheduled;
import org.springframework.stereotype.Service;
import javax.annotation.Resource;
import java.text.SimpleDateFormat;
import java.util.Date;
import java.util.concurrent.CountDownLatch;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.TimeUnit;
/**
* @author Andya
* @create 2020-05-29 14:26
*/
@Service
@EnableScheduling
@Slf4j
public class TestThreadPool {
@Resource(name = "firstThreadPool")
private ExecutorService firstThreadPool;
@Scheduled(cron = "0 * * * * *")
public void test1SchedulerThreadPool() {
final CountDownLatch countDownLatch = new CountDownLatch(5);
log.info("Begin schedule-【1】 startTime: {}", new SimpleDateFormat("yyyy-MM-dd HH:mm:ss").format(new Date()));
for (int i = 0; i < 5; i++) {
firstThreadPool.execute(() -> {
countDownLatch.countDown();
log.info("schedule-【1】 , threadPool info: {}, countDownLatch info: {}", firstThreadPool.toString(), countDownLatch.toString());
});
}
try {
countDownLatch.await(5, TimeUnit.MINUTES);
} catch (InterruptedException e) {
log.error("schedule-【1】timeout, {}", e.getMessage());
} finally {
log.info("schedule-【1】 multi-threading countDownLatch count: {}", countDownLatch.getCount());
}
log.info("End schedule-【1】 startTime: {}", new SimpleDateFormat("yyyy-MM-dd HH:mm:ss").format(new Date()));
}
@Scheduled(cron = "0 * * * * *")
public void test2SchedulerThreadPool() {
final CountDownLatch countDownLatch = new CountDownLatch(5);
log.info("Begin schedule-【2】 startTime: {}", new SimpleDateFormat("yyyy-MM-dd HH:mm:ss").format(new Date()));
for (int i = 0; i < 5; i++) {
firstThreadPool.execute(() -> {
countDownLatch.countDown();
log.info("schedule-【2】, threadPool info {}, countDownLatch info: {}", firstThreadPool.toString(), countDownLatch.toString());
});
}
try {
countDownLatch.await(5, TimeUnit.MINUTES);
} catch (InterruptedException e) {
log.error("schedule-【2】timeout, {}", e.getMessage());
} finally {
log.info("schedule-【2】 multi-threading countDownLatch count: {}", countDownLatch.getCount());
}
log.info("End schedule-【2】 startTime: {}", new SimpleDateFormat("yyyy-MM-dd HH:mm:ss").format(new Date()));
}
}
运行结果
2020-05-29 15:45:00.011 INFO 6900 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : Begin schedule-【2】 startTime: 2020-05-29 15:45:00
2020-05-29 15:45:00.018 INFO 6900 --- [t-thread-pool-0] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 5, active threads = 5, queued tasks = 0, completed tasks = 0], countDownLatch info: java.util.concurrent.CountDownLatch@522af59c[Count = 4]
2020-05-29 15:45:00.019 INFO 6900 --- [t-thread-pool-1] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 5, active threads = 4, queued tasks = 0, completed tasks = 1], countDownLatch info: java.util.concurrent.CountDownLatch@522af59c[Count = 3]
2020-05-29 15:45:00.019 INFO 6900 --- [t-thread-pool-2] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 5, active threads = 3, queued tasks = 0, completed tasks = 2], countDownLatch info: java.util.concurrent.CountDownLatch@522af59c[Count = 2]
2020-05-29 15:45:00.019 INFO 6900 --- [t-thread-pool-3] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 5, active threads = 2, queued tasks = 0, completed tasks = 3], countDownLatch info: java.util.concurrent.CountDownLatch@522af59c[Count = 1]
2020-05-29 15:45:00.019 INFO 6900 --- [t-thread-pool-4] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 5, active threads = 1, queued tasks = 0, completed tasks = 4], countDownLatch info: java.util.concurrent.CountDownLatch@522af59c[Count = 0]
2020-05-29 15:45:00.019 INFO 6900 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : schedule-【2】 multi-threading countDownLatch count: 0
2020-05-29 15:45:00.019 INFO 6900 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : End schedule-【2】 startTime: 2020-05-29 15:45:00
2020-05-29 15:45:00.020 INFO 6900 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : Begin schedule-【1】 startTime: 2020-05-29 15:45:00
2020-05-29 15:45:00.021 INFO 6900 --- [t-thread-pool-0] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 9, active threads = 5, queued tasks = 0, completed tasks = 5], countDownLatch info: java.util.concurrent.CountDownLatch@5ced01a9[Count = 4]
2020-05-29 15:45:00.023 INFO 6900 --- [t-thread-pool-5] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 9, active threads = 4, queued tasks = 0, completed tasks = 6], countDownLatch info: java.util.concurrent.CountDownLatch@5ced01a9[Count = 3]
2020-05-29 15:45:00.024 INFO 6900 --- [t-thread-pool-6] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 9, active threads = 3, queued tasks = 0, completed tasks = 7], countDownLatch info: java.util.concurrent.CountDownLatch@5ced01a9[Count = 2]
2020-05-29 15:45:00.024 INFO 6900 --- [t-thread-pool-7] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 9, active threads = 3, queued tasks = 0, completed tasks = 7], countDownLatch info: java.util.concurrent.CountDownLatch@5ced01a9[Count = 1]
2020-05-29 15:45:00.025 INFO 6900 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : schedule-【1】 multi-threading countDownLatch count: 0
2020-05-29 15:45:00.025 INFO 6900 --- [t-thread-pool-8] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@26b894bd[Running, pool size = 9, active threads = 3, queued tasks = 0, completed tasks = 7], countDownLatch info: java.util.concurrent.CountDownLatch@5ced01a9[Count = 0]
2020-05-29 15:45:00.025 INFO 6900 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : End schedule-【1】 startTime: 2020-05-29 15:45:00
从上述结果中可以看出,虽然是test1SchedulerThreadPool()和test2SchedulerThreadPool()都是每分钟执行定时任务,但是明显两个方法没有并发执行,而是串行执行的。
并发定时器模板
通过增加一个配置类来并发执行定时任务。
package com.example.andya.demo.conf;
import org.springframework.context.annotation.Configuration;
import org.springframework.scheduling.annotation.SchedulingConfigurer;
import org.springframework.scheduling.config.ScheduledTaskRegistrar;
import java.util.concurrent.Executors;
/**
* @author Andya
* @create 2020-05-29 15:52
*/
@Configuration
public class ScheduleConfig implements SchedulingConfigurer {
@Override
public void configureTasks(ScheduledTaskRegistrar scheduledTaskRegistrar) {
scheduledTaskRegistrar.setScheduler(Executors.newScheduledThreadPool(10));
}
}
运行结果
2020-05-29 15:53:00.005 INFO 3028 --- [pool-2-thread-2] c.e.andya.demo.service.TestThreadPool : Begin schedule-【2】 startTime: 2020-05-29 15:53:00
2020-05-29 15:53:00.015 INFO 3028 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : Begin schedule-【1】 startTime: 2020-05-29 15:53:00
2020-05-29 15:53:00.019 INFO 3028 --- [t-thread-pool-0] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 9, queued tasks = 1, completed tasks = 0], countDownLatch info: java.util.concurrent.CountDownLatch@630f649f[Count = 3]
2020-05-29 15:53:00.020 INFO 3028 --- [t-thread-pool-3] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 9, queued tasks = 1, completed tasks = 0], countDownLatch info: java.util.concurrent.CountDownLatch@630f649f[Count = 1]
2020-05-29 15:53:00.019 INFO 3028 --- [t-thread-pool-1] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 9, queued tasks = 1, completed tasks = 0], countDownLatch info: java.util.concurrent.CountDownLatch@630f649f[Count = 3]
2020-05-29 15:53:00.019 INFO 3028 --- [t-thread-pool-2] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 9, queued tasks = 1, completed tasks = 0], countDownLatch info: java.util.concurrent.CountDownLatch@630f649f[Count = 2]
2020-05-29 15:53:00.021 INFO 3028 --- [t-thread-pool-0] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 6, queued tasks = 0, completed tasks = 4], countDownLatch info: java.util.concurrent.CountDownLatch@5ebb120e[Count = 4]
2020-05-29 15:53:00.021 INFO 3028 --- [t-thread-pool-4] c.e.andya.demo.service.TestThreadPool : schedule-【2】, threadPool info java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 5, queued tasks = 0, completed tasks = 5], countDownLatch info: java.util.concurrent.CountDownLatch@630f649f[Count = 0]
2020-05-29 15:53:00.021 INFO 3028 --- [pool-2-thread-2] c.e.andya.demo.service.TestThreadPool : schedule-【2】 multi-threading countDownLatch count: 0
2020-05-29 15:53:00.022 INFO 3028 --- [pool-2-thread-2] c.e.andya.demo.service.TestThreadPool : End schedule-【2】 startTime: 2020-05-29 15:53:00
2020-05-29 15:53:00.022 INFO 3028 --- [t-thread-pool-5] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 4, queued tasks = 0, completed tasks = 6], countDownLatch info: java.util.concurrent.CountDownLatch@5ebb120e[Count = 3]
2020-05-29 15:53:00.022 INFO 3028 --- [t-thread-pool-6] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 3, queued tasks = 0, completed tasks = 7], countDownLatch info: java.util.concurrent.CountDownLatch@5ebb120e[Count = 2]
2020-05-29 15:53:00.024 INFO 3028 --- [t-thread-pool-7] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 2, queued tasks = 0, completed tasks = 8], countDownLatch info: java.util.concurrent.CountDownLatch@5ebb120e[Count = 1]
2020-05-29 15:53:00.024 INFO 3028 --- [t-thread-pool-8] c.e.andya.demo.service.TestThreadPool : schedule-【1】 , threadPool info: java.util.concurrent.ThreadPoolExecutor@5149f008[Running, pool size = 9, active threads = 2, queued tasks = 0, completed tasks = 8], countDownLatch info: java.util.concurrent.CountDownLatch@5ebb120e[Count = 0]
2020-05-29 15:53:00.024 INFO 3028 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : schedule-【1】 multi-threading countDownLatch count: 0
2020-05-29 15:53:00.024 INFO 3028 --- [pool-2-thread-1] c.e.andya.demo.service.TestThreadPool : End schedule-【1】 startTime: 2020-05-29 15:53:00
可以从运行结果中看到,test1SchedulerThreadPool()和test2SchedulerThreadPool()两个方法同时打印了Begin schedule...信息,是并发定时。
SpringBoot—自定义线程池及并发定时任务模板的更多相关文章
- SpringBoot自定义线程池处理异步任务
@Async异步调用 就不解释什么是异步调用了,Spring Boot中进行异步调用很简单 1.通过使用@Async注解就能简单的将原来的同步函数变为异步函数 package com.winner.s ...
- SpringBoot 自定义线程池
本教程目录: 自定义线程池 配置spring默认的线程池 1. 自定义线程池 1.1 修改application.properties task.pool.corePoolSize=20 task.p ...
- SpringBoot 自定义线程池,多线程
原文:https://www.jianshu.com/p/832f2b162450 我们都知道spring只是为我们简单的处理线程池,每次用到线程总会new 一个新的线程,效率不高,所以我们需要自定义 ...
- JAVA并发,线程工厂及自定义线程池
package com.xt.thinks21_2; import java.util.concurrent.ExecutorService; import java.util.concurrent. ...
- Spring Boot使用@Async实现异步调用:自定义线程池
前面的章节中,我们介绍了使用@Async注解来实现异步调用,但是,对于这些异步执行的控制是我们保障自身应用健康的基本技能.本文我们就来学习一下,如果通过自定义线程池的方式来控制异步调用的并发. 定义线 ...
- 转载-SpringBoot结合线程池解决多线程问题实录;以及自己的总结
原文地址:https://blog.csdn.net/GFJ0814/article/details/92422245 看看这篇文章(继续学习):https://www.jianshu.com/p/3 ...
- Android AsyncTask 深度理解、简单封装、任务队列分析、自定义线程池
前言:由于最近在做SDK的功能,需要设计线程池.看了很多资料不知道从何开始着手,突然发现了AsyncTask有对线程池的封装,so,就拿它开刀,本文将从AsyncTask的基本用法,到简单的封装,再到 ...
- Android 自定义线程池的实战
前言:在上一篇文章中我们讲到了AsyncTask的基本使用.AsyncTask的封装.AsyncTask 的串行/并行线程队列.自定义线程池.线程池的快速创建方式. 对线程池不了解的同学可以先看 An ...
- spring boot / cloud (四) 自定义线程池以及异步处理@Async
spring boot / cloud (四) 自定义线程池以及异步处理@Async 前言 什么是线程池? 线程池是一种多线程处理形式,处理过程中将任务添加到队列,然后在创建线程后自动启动这些任务.线 ...
随机推荐
- Fiddler 介绍
1.fiddler原理介绍 fiddler 是一个抓包工具,当浏览器访问服务器会形成一个请求,此时,fiddler就处于请求之间,当浏览器发送请求,会先经过 fiddler,然后在到服务器:当服务器有 ...
- 「译」JVM是如何使用那些你从未听过的x86魔幻指令实现String.compareTo的
原文https://jcdav.is/2016/09/01/How-the-JVM-compares-your-strings/ 魔幻的String.compareTo 我们之前可能已经见过Java的 ...
- 《新版阿里巴巴Java开发手册》提到的三目运算符的空指针问题到底是个怎么回事?
最近,阿里巴巴Java开发手册发布了最新版--泰山版,这个名字起的不错,一览众山小. 新版新增了30+规约,其中有一条规约引起了作者的关注,那就是手册中提到在三目运算符使用过程中,需要注意自动拆箱导致 ...
- wmic 内网使用
先决条件: 1.远程服务器启动Windows Management Instrumentation服务,开放TCP135端口,防火墙放开对此端口的流量(默认放开): 2.远程服务器的本地安全策略的“网 ...
- React Native超简单完整示例-tabs、页面导航、热更新、用户行为分析
初学React Native,如果没有人指引,会发现好多东西无从下手,但当有人指引后,会发现其实很简单.这也是本人写这篇博客的主要原因,希望能帮到初学者. 本文不会介绍如何搭建开发环境,如果你还没有搭 ...
- Spring官网阅读(十五)Spring中的格式化(Formatter)
文章目录 Formatter 接口定义 继承树 注解驱动的格式化 AnnotationFormatterFactory FormatterRegistry 接口定义 UML类图 FormattingC ...
- python gdal 写GeoTiff文件
1.gdal数据类型 (1)GDT_Byte(int8) (2)GDT_UInt16 (3)GDT_Int16 (4)GDT_UInt32 (5)GDT_Int32 (6)GDT_Float3 ...
- JDBC11 封装+资源配置文件管理
封装为Utils类+程序资源文件去配置 public class Utils { static Properties p=null; static { p=new Properties(); try ...
- springmvc 文件上传异步处理
springmvc3提供了文件上传异步处理功能,当文件上传时,controller不需要一直等到文件上传成功后再返回视图,而是先返回到servlet容器,待异步处理的线程完成后转向指定视图! 首先要在 ...
- video 全屏,播放,隐藏控件。
requestFullscreen全屏具体实现 1.进入全屏 function full(ele) { if (ele.requestFullscreen) { ele.requestFullscre ...