/**
     * Executes the task with the specified parameters. The task returns
     * itself (this) so that the caller can keep a reference to it.
     *
     * <p>This method is typically used with {@link #THREAD_POOL_EXECUTOR} to
     * allow multiple tasks to run in parallel on a pool of threads managed by
     * AsyncTask, however you can also use your own {@link Executor} for custom
     * behavior.
     *
     * <p><em>Warning:</em> Allowing multiple tasks to run in parallel from
     * a thread pool is generally <em>not</em> what one wants, because the order
     * of their operation is not defined.  For example, if these tasks are used
     * to modify any state in common (such as writing a file due to a button click),
     * there are no guarantees on the order of the modifications.
     * Without careful work it is possible in rare cases for the newer version
     * of the data to be over-written by an older one, leading to obscure data
     * loss and stability issues.  Such changes are best
     * executed in serial; to guarantee such work is serialized regardless of
     * platform version you can use this function with {@link #SERIAL_EXECUTOR}.
     *
     * <p>This method must be invoked on the UI thread.
     *
     * @param exec The executor to use.  {@link #THREAD_POOL_EXECUTOR} is available as a
     *              convenient process-wide thread pool for tasks that are loosely coupled.
     * @param params The parameters of the task.
     *
     * @return This instance of AsyncTask.
     *
     * @throws IllegalStateException If {@link #getStatus()} returns either
     *         {@link AsyncTask.Status#RUNNING} or {@link AsyncTask.Status#FINISHED}.
     *
     * @see #execute(Object[])
     */
    public final AsyncTask<Params, Progress, Result> executeOnExecutor(Executor exec,
            Params... params) {}



    当我执行两次调用asyncTask.execute(task);时发现只有当第一次的任务完成后才执行下一下任务！！怎么回事？

AyncTask不是号称异步线程池吗？既然是线程池那么多任务执行时应该可以并发执行啊，至少两个任务可以并发执

行，以前看过一个视频，人家的就可以啊！纠结了一下午，通过查阅资料和自己的动手实验终于把问题搞明白了。

    原来在SDK3.0以前的版本执行asyncTask.execute(task);时的确是多线程并发执行的，线程池大小为5，最大可大

128个，google在3.0以后的版本中做了修改，将asyncTask.execute(task);修改为了顺序执行，即只有当一个的实例

的任务完成后在执行下一个实例的任务。

ExecutorObject... params)，

该方法接受2个参数，第一个是Executor，第二个是任务参数。第一个是线程池实例，google为我们预定义了两种：

第一种是AsyncTask.SERIAL_EXECUTOR，第二种是AsyncTask.THREAD_POOL_EXECUTOR，顾名思义，第一

种其实就像3.0以后的execute方法，是顺序执行的。第二种就是3.0以前的execute方法，是可以并发执行的。我们直

接用asyncTask.executeOnExecutor(AsyncTask.THREAD_POOL_EXECUTOR, task);就可以多任务并发执行了。

    既然executeOnExecutor第一个参数是Executor，那么我们可以自定义Executor吗？当然可以，Executor主要由四

种类型newCachedThreadPool，newFixedThreadPool，newScheduledThreadPool，newSingleThreadExecutor

（具体使用解析可以看我上一篇文章点击打开链接），可是当我这样使用

asyncTask.executeOnExecutor(Executors.newFixedThreadPool(1), task);或者

asyncTask.executeOnExecutor(Executors.newSingleThreadExecutor, task);并没有像我想象的与

asyncTask.executeOnExecutor(AsyncTask.SERIAL_EXECUTOR, task);那样是单线程顺序执行，而是像

asyncTask.executeOnExecutor(AsyncTask.THREAD_POOL_EXECUTOR, task);是多线程并发执行的，我不是

已经规定newFixedThreadPool的线程池数量是1或者是newSingleThreadExecutor单线程了么！怎么回事呢？原来程

序在每次调用asyncTask.executeOnExecutor(Executors.newFixedThreadPool(2), task)时会获取一个新的Executor对

象，这个对象内的线程只执行对应的task，所以无论哪种情况每个task都有一个新的线程来执行，即并发执行。

知道原因就好办了，我们定义个一全局静态变量

private static ExecutorService exec = Executors.newSingleThreadExecutor();程序在每次调用

asyncTask.executeOnExecutor(exec, task);时是使用的同一个Executor，执行效果如下：

当Executor类型为：private static ExecutorService exec = Executors.newFixedThreadPool(2);只有两个线程在执行

任务

AsyncTask executeOnExecutor_android

当Executor类型为：private static ExecutorService exec = Executors.newSingleThreadExecutor();只有一个线程在执行任务

AsyncTask executeOnExecutor_单线程_02