ThreadPoolExecutor Self‑Introduction: Core Concepts, Parameters and Lifecycle

ThreadPoolExecutor is a Java component that manages a pool of worker threads to execute tasks concurrently while minimizing the overhead of creating and destroying threads, which involves costly system calls and kernel resources.

Each thread maps to a native kernel thread, consuming stack memory (default 1 MB). Creating a new thread for every task would quickly exhaust memory and system resources.

corePoolSize

The pool keeps a set of core threads (default 3 in this example) that stay alive even when idle, reducing the time spent on thread creation and destruction. When a task is submitted via execute(Runnable command) , the pool creates core threads until the corePoolSize is reached.

public interface Executor {
    void execute(Runnable command);
}

If the number of core threads is below corePoolSize, new core threads are created regardless of whether existing core threads are idle, ensuring the pool quickly reaches its configured capacity.

workQueue

When core threads are all busy, incoming tasks are placed into a workQueue. A bounded blocking queue is recommended; otherwise an unbounded queue can grow indefinitely, leading to OutOfMemoryError (OOM) when task production outpaces consumption.

The queue blocks consumer threads when empty, preventing busy‑waiting and CPU waste.

maximumPoolSize

If the workQueue becomes full and the total number of threads is still below maximumPoolSize (e.g., 5), the pool creates additional non‑core threads to handle the overflow.

RejectedExecutionHandler

When both the workQueue is full and the pool has reached maximumPoolSize, further task submissions are handled by a RejectedExecutionHandler, which by default throws a RejectedExecutionException . Java provides several policies such as AbortPolicy, DiscardPolicy, DiscardOldestPolicy, CallerRunsPolicy, or a custom handler.

keepAliveTime

Threads that exceed corePoolSize are terminated if they remain idle for longer than keepAliveTime, allowing the pool to shrink back to corePoolSize and release resources.

Summary

The article gives a high‑level overview of ThreadPoolExecutor's operation. For a deeper understanding, readers are encouraged to study the source code in detail.