一、概述
在java doc中，并不提倡我们直接使用ThreadPoolExecutor，而是使用Executors类中提供的几个静态方法来创建线程池：
以下方法是Executors下的静态方法，Executors中所定义的 Executor、ExecutorService、ScheduledExecutorService、ThreadFactory 和 Callable 类的工厂和实用方法。
Executors只是一个工厂类，它所有的方法返回的都是ThreadPoolExecutor、ScheduledThreadPoolExecutor这两个类的实例。一共可以创建四种线程池。
1.1、基础类
import java.text.SimpleDateFormat; import java.util.Date; import java.util.concurrent.TimeUnit; public class TestThread implements Runnable { // 线程私有属性，创建线程时创建 private Integer num = 0; public TestThread(Integer num) { this.num = num; } @Override public void run() { SimpleDateFormat sdf1 = new SimpleDateFormat("yyyy-MM-dd hh:mm:ss"); System.out.println("thread:" + Thread.currentThread().getName() + ",time:" + sdf1.format(new Date()) + ",num:" + num); try { //使线程睡眠，模拟线程阻塞情况 TimeUnit.SECONDS.sleep(3); } catch (InterruptedException e) { e.printStackTrace(); } System.out.println("task "+num+"执行完毕"); } }
0、使用ThreadPoolExecutor 创建使用
public static void testThreadPoolExecutor() { ThreadPoolExecutor executor = new ThreadPoolExecutor(5, 10, 200, TimeUnit.MILLISECONDS, new ArrayBlockingQueue<Runnable>(5)); for (int i = 0; i < 15; i++) { TestThread myTask = new TestThread(i); executor.execute(myTask); System.out.println("线程池中线程数目：" + executor.getPoolSize() + "，队列中等待执行的任务数目：" + executor.getQueue().size() + "，已执行玩别的任务数目：" + executor.getCompletedTaskCount()); } executor.shutdown(); }
输出：
/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/bin/java "-javaagent:/Applications/IntelliJ IDEA.app/Contents/lib/idea_rt.jar=54880:/Applications/IntelliJ IDEA.app/Contents/bin" -Dfile.encoding=UTF-8 -classpath /Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/charsets.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/deploy.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/cldrdata.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/jaccess.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/jfxrt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/nashorn.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/javaws.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/jce.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/jfr.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/jfxswt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/jsse.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/management-agent.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/plugin.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/resources.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/jre/lib/rt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/lib/ant-javafx.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/lib/dt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/lib/javafx-mx.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/lib/jconsole.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/lib/packager.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/lib/sa-jdi.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_172.jdk/Contents/Home/lib/tools.jar:/Users/lihongxu6/IdeaProjects/java-data-structure-algorithm/data-005-jdkstruct/target/classes:/Users/lihongxu6/.m2/repository/junit/junit/4.11/junit-4.11.jar com.github.bjlhx15.datastructure.algorithm.thread.ThreadPoolDemo2 线程池中线程数目：1，队列中等待执行的任务数目：0，已执行完的任务数目：0 线程池中线程数目：2，队列中等待执行的任务数目：0，已执行完的任务数目：0 线程池中线程数目：3，队列中等待执行的任务数目：0，已执行完的任务数目：0 线程池中线程数目：4，队列中等待执行的任务数目：0，已执行完的任务数目：0 线程池中线程数目：5，队列中等待执行的任务数目：0，已执行完的任务数目：0 线程池中线程数目：5，队列中等待执行的任务数目：1，已执行完的任务数目：0 线程池中线程数目：5，队列中等待执行的任务数目：2，已执行完的任务数目：0 线程池中线程数目：5，队列中等待执行的任务数目：3，已执行完的任务数目：0 线程池中线程数目：5，队列中等待执行的任务数目：4，已执行完的任务数目：0 线程池中线程数目：5，队列中等待执行的任务数目：5，已执行完的任务数目：0 线程池中线程数目：6，队列中等待执行的任务数目：5，已执行完的任务数目：0 线程池中线程数目：7，队列中等待执行的任务数目：5，已执行完的任务数目：0 线程池中线程数目：8，队列中等待执行的任务数目：5，已执行完的任务数目：0 线程池中线程数目：9，队列中等待执行的任务数目：5，已执行完的任务数目：0 线程池中线程数目：10，队列中等待执行的任务数目：5，已执行完的任务数目：0 thread:pool-1-thread-6,time:2019-06-19 06:10:53,num:10 thread:pool-1-thread-2,time:2019-06-19 06:10:53,num:1 thread:pool-1-thread-7,time:2019-06-19 06:10:53,num:11 thread:pool-1-thread-5,time:2019-06-19 06:10:53,num:4 thread:pool-1-thread-9,time:2019-06-19 06:10:53,num:13 thread:pool-1-thread-8,time:2019-06-19 06:10:53,num:12 thread:pool-1-thread-4,time:2019-06-19 06:10:53,num:3 thread:pool-1-thread-10,time:2019-06-19 06:10:53,num:14 thread:pool-1-thread-1,time:2019-06-19 06:10:53,num:0 thread:pool-1-thread-3,time:2019-06-19 06:10:53,num:2 task 11执行完毕 task 14执行完毕 task 12执行完毕 task 0执行完毕 task 2执行完毕 task 3执行完毕 task 13执行完毕 task 1执行完毕 task 10执行完毕 task 4执行完毕 thread:pool-1-thread-3,time:2019-06-19 06:10:56,num:9 thread:pool-1-thread-1,time:2019-06-19 06:10:56,num:8 thread:pool-1-thread-10,time:2019-06-19 06:10:56,num:7 thread:pool-1-thread-8,time:2019-06-19 06:10:56,num:6 thread:pool-1-thread-7,time:2019-06-19 06:10:56,num:5 task 8执行完毕 task 5执行完毕 task 7执行完毕 task 9执行完毕 task 6执行完毕 Process finished with exit code 0