Java 线程池之源码解析

 

 

Executors为线程池工具类，主要可创建
创建固定数量线程数的线程池，不回收
public static ExecutorService newFixedThreadPool(int nThreads) {
    return new ThreadPoolExecutor(nThreads, nThreads,
                                  0L, TimeUnit.MILLISECONDS,
                                  new LinkedBlockingQueue<Runnable>());
}

创建线程可回收的线程池，并且可以全部回收
public static ExecutorService newCachedThreadPool() {
    return new ThreadPoolExecutor(0, Integer.MAX_VALUE,
                                  60L, TimeUnit.SECONDS,
                                  new SynchronousQueue<Runnable>());
}

创建定时执行线程池
public static ScheduledExecutorService newScheduledThreadPool(int corePoolSize) {
    return new ScheduledThreadPoolExecutor(corePoolSize);
}

创建单个线程的线程池
public static ExecutorService newSingleThreadExecutor(ThreadFactory threadFactory) {
    return new FinalizableDelegatedExecutorService
        (new ThreadPoolExecutor(1, 1,
                                0L, TimeUnit.MILLISECONDS,
                                new LinkedBlockingQueue<Runnable>(),
                                threadFactory));
}
二、ThreadPoolExecutor线程池类参数详解
参数说明corePoolSize核心线程数量，线程池维护线程的最少数量maximumPoolSize线程池维护线程的最大数量keepAliveTime线程池除核心线程外的其他线程的最长空闲时间，超过该时间的空闲线程会被销毁unitkeepAliveTime的单位，TimeUnit中的几个静态属性：NANOSECONDS、MICROSECONDS、MILLISECONDS、SECONDSworkQueue线程池所使用的任务缓冲队列threadFactory线程工厂，用于创建线程，一般用默认的即可handler线程池对拒绝任务的处理策略

上面工具类阿里规范是不建议使用，需要使用者自己知道每个参数的意思，并自己设定，从而知道内部原理，防止资源耗尽，
下面主要看一下ThreadPoolExecutor：

几个类的主要方法：
Executor->void execute(Runnable command);
ExecutorService->Future<?> submit(Runnable task);
AbstractExecutorService
public Future<?> submit(Runnable task) {
    if (task == null) throw new NullPointerException();
    RunnableFuture<Void> ftask = newTaskFor(task, null);
    execute(ftask);
    return ftask;
}
使用模板方法，调用子类的execute方法；
再来看看
RunnableFuture继承Runnable, Future
同时
FutureTask实现RunnableFuture,构造函数：
public FutureTask(Callable<V> callable) {
    if (callable == null)
        throw new NullPointerException();
    this.callable = callable;
    this.state = NEW;       // ensure visibility of callable
}
public FutureTask(Runnable runnable, V result) {
    this.callable = Executors.callable(runnable, result);
    this.state = NEW;       // ensure visibility of callable
}
同时实现run方法：
public void run() {
    if (state != NEW ||
        !UNSAFE.compareAndSwapObject(this, runnerOffset,
                                     null, Thread.currentThread()))
        return;
    try {
        Callable<V> c = callable;
        if (c != null && state == NEW) {
            V result;
            boolean ran;
            try {
                result = c.call();
                ran = true;
            } catch (Throwable ex) {
                result = null;
                ran = false;
                setException(ex);
            }
            if (ran)
                set(result);
        }
    } finally {
        // runner must be non-null until state is settled to
        // prevent concurrent calls to run()
        runner = null;
        // state must be re-read after nulling runner to prevent
        // leaked interrupts
        int s = state;
        if (s >= INTERRUPTING)
            handlePossibleCancellationInterrupt(s);
    }
}
可以看到FutureTask调用run方法时，调用Callable的call方法，将执行结果设置到Object outcome，get的时候返回Object outcome，好了，我们知道是如何获取结果了。
接下来我们来分析execute(ftask);这个方法有具体实现类实现。
我们来看ThreadPoolExecutor如何实现：
public void execute(Runnable command) {
    if (command == null)
        throw new NullPointerException();
    /*
     * Proceed in 3 steps:
     *
     * 1. If fewer than corePoolSize threads are running, try to
     * start a new thread with the given command as its first
     * task.  The call to addWorker atomically checks runState and
     * workerCount, and so prevents false alarms that would add
     * threads when it shouldn't, by returning false.
     *
     * 2. If a task can be successfully queued, then we still need
     * to double-check whether we should have added a thread
     * (because existing ones died since last checking) or that
     * the pool shut down since entry into this method. So we
     * recheck state and if necessary roll back the enqueuing if
     * stopped, or start a new thread if there are none.
     *
     * 3. If we cannot queue task, then we try to add a new
     * thread.  If it fails, we know we are shut down or saturated
     * and so reject the task.
     */
    int c = ctl.get();
    if (workerCountOf(c) < corePoolSize) {
        if (addWorker(command, true))
            return;
        c = ctl.get();
    }
    if (isRunning(c) && workQueue.offer(command)) {
        int recheck = ctl.get();
        if (! isRunning(recheck) && remove(command))
            reject(command);
        else if (workerCountOf(recheck) == 0)
            addWorker(null, false);
    }
    else if (!addWorker(command, false))
        reject(command);
}
说一下线程池状态和数量的获取：
在ThreadPoolExecutor，整型中32位的前3位用来表示线程池状态，后3位表示线程池中有效的线程数。
// 得到线程数，也就是后29位的数字。 直接跟CAPACITY做一个与操作即可，CAPACITY就是的值就 1 << 29 - 1 = 00011111111111111111111111111111。 与操作的话前面3位肯定为0，相当于直接取后29位的值
private static int workerCountOf(int c)  { return c & CAPACITY; }

// 得到状态，CAPACITY的非操作得到的二进制位11100000000000000000000000000000，然后做在一个与操作，相当于直接取前3位的的值
private static int runStateOf(int c)     { return c & ~CAPACITY; }

// 或操作。相当于获取数量和状态两个操作
private static int ctlOf(int rs, int wc) { return rs | wc; }
看代码前我们先看一个流程图：

如果新进来任务：
1，核心线程数未满，直接创建线程执行
2，核心线程数达到上限，看阻塞队列是否已满，未满直接放入任务队列中
3，如果队列已满，看最大线程数是否已满，未满创建线程执行
4，如果最大线程数达到上限，执行拒绝策略：
AbortPolicy
ThreadPoolExecutor.AbortPolicy:丢弃任务并抛出RejectedExecutionException异常。

DiscardPolicy
ThreadPoolExecutor.DiscardPolicy：丢弃任务，但是不抛出异常。如果线程队列已满，则后续提交的任务都会被丢弃，且是静默丢弃。

DiscardOldestPolicy
ThreadPoolExecutor.DiscardOldestPolicy：丢弃队列最前面的任务，然后重新提交被拒绝的任务。

CallerRunsPolicy
ThreadPoolExecutor.CallerRunsPolicy：由调用线程处理该任务
好了，再来看一下这段：
if (isRunning(c) && workQueue.offer(command)) {//如果线程池正常执行，同时加入队列成功
        int recheck = ctl.get();	//再次获取线程池状态
        if (! isRunning(recheck) && remove(command)) //检查当前线程池是否关闭，如果!isRunning(recheck)（c >= SHUTDOWN）既线程池立即关闭，同时不执行新的任务，那么要删除刚刚加入的任务
            reject(command);
        else if (workerCountOf(recheck) == 0) //这里是当线程池没有运行的线程，那么核心线程数肯定设置成0，被回收完，这个时候使用maximumPoolSize
            addWorker(null, false);//
    }
好了段代码对应上面流程图。
再说一下addWorker：
private boolean addWorker(Runnable firstTask, boolean core) {
    retry:
    for (;;) {
        int c = ctl.get();
        int rs = runStateOf(c);

        // 检查线程池是SHUTDOWN还是STOP，TIDYING,TERMINATED这些状态都是不能执行新的任务
        if (rs >= SHUTDOWN &&
            ! (rs == SHUTDOWN &&
               firstTask == null &&
               ! workQueue.isEmpty()))
            return false;

        for (;;) {
            //如果线程池当前执行线程数超出指定数量则不执行
            int wc = workerCountOf(c);
            if (wc >= CAPACITY ||
                wc >= (core ? corePoolSize : maximumPoolSize))
                return false;
    	//cas自增当前线程池的线程数
            if (compareAndIncrementWorkerCount(c))
                break retry;
    	//再次检查一次线程池状态是否和开始的状态一致
            c = ctl.get();  // Re-read ctl
            if (runStateOf(c) != rs)
                continue retry;
            // else CAS failed due to workerCount change; retry inner loop
        }
    }

    boolean workerStarted = false;
    boolean workerAdded = false;
    Worker w = null;
    try {
        //构造Worker，通过getThreadFactory().newThread(this)添加线程，getThreadFactory()就是我们添加的线程工厂，没配就用默认DefaultThreadFactory
        w = new Worker(firstTask);
        final Thread t = w.thread;
        if (t != null) {
            final ReentrantLock mainLock = this.mainLock;
            mainLock.lock();
            try {
                // Recheck while holding lock.
                // Back out on ThreadFactory failure or if
                // shut down before lock acquired.
                int rs = runStateOf(ctl.get());
    		//检查一次线程池状态
                if (rs < SHUTDOWN ||
                    (rs == SHUTDOWN && firstTask == null)) {
                    if (t.isAlive()) // precheck that t is startable
                        throw new IllegalThreadStateException();
                        //将创建的worker加入HashSet队列中，由于HashSet非线程安全，上下通过加锁防止并发
                    workers.add(w);
                    int s = workers.size();
                    if (s > largestPoolSize)
                        largestPoolSize = s;
                    workerAdded = true;
                }
            } finally {
                mainLock.unlock();
            }
            if (workerAdded) {
                //加入成功执行worker中的线程
                t.start();
                workerStarted = true;
            }
        }
    } finally {
        if (! workerStarted)
        	//如果worker线程执行失败回滚
            addWorkerFailed(w);
    }
    return workerStarted;
}

好了，看上面注释基本结束，再来看看Worker，Worker继承AQS，同时也是Runnable，所以线程执行会执行内部run方法。
注意：线程池有一个Runnable队列和一个HashSet的工作集合
Worker
    extends AbstractQueuedSynchronizer
    implements Runnable
public void run() {
    runWorker(this);
}
final void runWorker(Worker w) {
    Thread wt = Thread.currentThread();
    Runnable task = w.firstTask;
    w.firstTask = null;
    w.unlock(); // allow interrupts
    boolean completedAbruptly = true;
    try {
        //如果task等于空，则为回收线程，继续循环去任务队列获取任务执行
    	while (task != null || (task = getTask()) != null) {
         	// 上锁，表示当前Worker已经要开始执行任务，不是闲置Worker
            w.lock();
            // 在执行任务之前先做一些处理。
            // 1. 如果线程池已经处于STOP状态，则中断线程 
            //2. 如果线程池还处于RUNNING或SHUTDOWN状态，并且当前线程已经被中断了，重新检查一下线程池状态，如果处于STOP状态并且没有被中断，那么中断线程
            if ((runStateAtLeast(ctl.get(), STOP) ||
                 (Thread.interrupted() &&
                  runStateAtLeast(ctl.get(), STOP))) &&
                !wt.isInterrupted())
                wt.interrupt();
            try {
                //前置执行(空)
                beforeExecute(wt, task);
                Throwable thrown = null;
                try {
                    //执行任务run方法
    		task.run();
                } catch (RuntimeException x) {
                    thrown = x; throw x;
                } catch (Error x) {
                    thrown = x; throw x;
                } catch (Throwable x) {
                    thrown = x; throw new Error(x);
                } finally {
                    //后置执行(空)
                    afterExecute(task, thrown);
                }
            } finally {
                task = null;
                w.completedTasks++;
                w.unlock();
            }
        }
        completedAbruptly = false;
    } finally {
        //回收worker
    processWorkerExit(w, completedAbruptly);
    }
}

看一下获取任务getTask：
private Runnable getTask() {
    boolean timedOut = false; // Did the last poll() time out?

    for (;;) {
        int c = ctl.get();
        int rs = runStateOf(c);

        // 如果线程池关闭，或者任务队列空停止执行新的任务
        if (rs >= SHUTDOWN && (rs >= STOP || workQueue.isEmpty())) {
            decrementWorkerCount();
            return null;
        }

        int wc = workerCountOf(c);

        // Are workers subject to culling?
        boolean timed = allowCoreThreadTimeOut || wc > corePoolSize;
    	//如果当前线程数大于maximumPoolSize，或者核心线程数设置超时，同时线程池有线程，这个时候任务队列空，停止执行新的任务
        if ((wc > maximumPoolSize || (timed && timedOut))
            && (wc > 1 || workQueue.isEmpty())) {
            if (compareAndDecrementWorkerCount(c))
                return null;
            continue;
        }

        try {
            //设置超时回收，则有限阻塞获取任务，否则一直阻塞，直到中断返回
            Runnable r = timed ?
                workQueue.poll(keepAliveTime, TimeUnit.NANOSECONDS) :
                workQueue.take();
            if (r != null)
                return r;
            timedOut = true;
        } catch (InterruptedException retry) {
            timedOut = false;
        }
    }
}
获取任务完结，同时看到有何优雅退出执行的线程，通过条件判断，同时捕获中断异常，设置条件变量
看一下回收：
private void processWorkerExit(Worker w, boolean completedAbruptly) {
    //标识是正常结束还是异常结束
    if (completedAbruptly) 
        decrementWorkerCount();

    final ReentrantLock mainLock = this.mainLock;
    mainLock.lock();
    try {
        completedTaskCount += w.completedTasks;
        //移除worker
        workers.remove(w);
    } finally {
        mainLock.unlock();
    }
    // 试着结束线程池
    tryTerminate();

    int c = ctl.get();
    //如果当前线程池正常执行，同时线程非异常结束，那么如果核心线程数设置回收空闲时间allowCoreThreadTimeOut=true，不会创建线程，
    //或者设置allowCoreThreadTimeOut=false,那么当超过核心线程数，也不会创建线程
    if (runStateLessThan(c, STOP)) {
        if (!completedAbruptly) {
            int min = allowCoreThreadTimeOut ? 0 : corePoolSize;
            if (min == 0 && ! workQueue.isEmpty())
                min = 1;
            if (workerCountOf(c) >= min)
                return; // replacement not needed
        }
        addWorker(null, false);
    }
}
说明：allowCoreThreadTimeOut这个方法允许Core Thread超时后可以关闭，The 也就是说可以单独对核心线程数进行空闲回收，但如果核心线程数设置为0，这个allowCoreThreadTimeOut设置也就没意义了，因为这个时候的空闲回收机制有最大线程数控制

public void shutdown() {
    final ReentrantLock mainLock = this.mainLock;
    mainLock.lock(); // 加锁，防止并发
    try {
        checkShutdownAccess(); // 检查线程池的权限
        advanceRunState(SHUTDOWN); // 状态更新到SHUTDOWN
        interruptIdleWorkers(); // 中断闲置的Worker
        onShutdown(); // 钩子方法，默认不处理。ScheduledThreadPoolExecutor会做一些处理
    } finally {
        mainLock.unlock(); // 解锁
    }
    tryTerminate(); // 尝试结束线程池
}