Custom thread pool configuration in Spring Boot - Step-by-Step Execution

Concept Flow - Custom thread pool configuration

Define ThreadPoolTaskExecutor Bean

↓

Set corePoolSize, maxPoolSize, queueCapacity

↓

Initialize ThreadPoolTaskExecutor

↓

Inject Executor in Service

↓

Submit Tasks to Executor

↓

Tasks run concurrently with configured threads

↓

Shutdown Executor on app stop

This flow shows how Spring Boot creates and uses a custom thread pool to run tasks concurrently with your specified settings.

Execution Sample

Spring Boot

  @Bean
  public ThreadPoolTaskExecutor taskExecutor() {
    ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
    executor.setCorePoolSize(2);
    executor.setMaxPoolSize(4);
    executor.setQueueCapacity(10);
    executor.initialize();
    return executor;
  }

Defines a thread pool with 2 core threads, max 4 threads, and a queue that holds 10 tasks waiting.

Execution Table

Step	Action	ThreadPool State	Task Submitted	Thread Used	Queue Size
1	Initialize ThreadPoolTaskExecutor	core=2, max=4, queue=empty	No	0	0
2	Submit Task 1	core=2, max=4, queue=empty	Yes	1	0
3	Submit Task 2	core=2, max=4, queue=empty	Yes	2	0
4	Submit Task 3	core=2, max=4, queue=1 task waiting	Yes	2	1
5	Submit Task 4	core=2, max=4, queue=2 tasks waiting	Yes	2	2
6	Submit Task 5	core=2, max=4, queue=3 tasks waiting	Yes	2	3
7	Submit Task 6	core=2, max=4, queue=4 tasks waiting	Yes	2	4
8	Submit Task 7	core=2, max=4, queue=5 tasks waiting	Yes	2	5
9	Submit Task 8	core=2, max=4, queue=6 tasks waiting	Yes	2	6
10	Submit Task 9	core=2, max=4, queue=7 tasks waiting	Yes	2	7
11	Submit Task 10	core=2, max=4, queue=8 tasks waiting	Yes	2	8
12	Submit Task 11	core=2, max=4, queue=9 tasks waiting	Yes	2	9
13	Submit Task 12	core=2, max=4, queue=10 tasks waiting (full)	Yes	2	10
14	Submit Task 13	core=2, max=4, queue=10 tasks waiting (full)	Yes	3	10
15	Submit Task 14	core=2, max=4, queue=10 tasks waiting (full)	Yes	4	10
16	Submit Task 15	Rejected - queue full and max threads reached	Yes	4	10

💡 Task 15 rejected because max threads (4) are busy and queue (capacity 10) is full.

Variable Tracker

Variable	Start	After Task 1	After Task 4	After Task 10	After Task 14	Final
Active Threads	0	1	2	2	4	4
Queue Size	0	0	2	8	10	10
Tasks Rejected	0	0	0	0	0	1

Key Moments - 3 Insights

Why does the thread pool start with 0 active threads but can run tasks immediately?

The pool creates threads lazily. It starts with 0 but creates up to corePoolSize (2) threads as tasks come in, shown in rows 2-3 of execution_table.

What happens when the queue is full and max threads are busy?

New tasks are rejected because no threads or queue space are available, as seen in step 16 of execution_table.

Why does the queue start filling only after 2 tasks are submitted?

Because corePoolSize is 2, the pool creates threads up to 2 before queuing tasks, so queue fills starting from task 3 (row 4).

Visual Quiz - 3 Questions

Look at the execution_table, how many threads are active after submitting Task 3?

A 4

B 2

C 3

D 1

💡 Hint

Check the 'Thread Used' column at Step 4 in execution_table.

At which step does the queue first start holding tasks?

A Step 4

B Step 6

C Step 2

D Step 10

💡 Hint

Look at the 'Queue Size' column in execution_table to find when it changes from 0.

If maxPoolSize was increased to 6, what would happen at Step 16?

A Queue size would increase beyond 10

B Task 15 would still be rejected

C Task 15 would be accepted and run immediately

D Core pool size would increase automatically

💡 Hint

Consider that more threads can be created up to maxPoolSize before rejecting tasks.

Concept Snapshot

Define a ThreadPoolTaskExecutor bean in Spring Boot.
Set corePoolSize, maxPoolSize, and queueCapacity.
Core threads run tasks immediately.
Extra tasks queue until full.
Max threads handle overflow.
Tasks rejected if queue and threads full.

Full Transcript

This visual execution shows how to configure a custom thread pool in Spring Boot using ThreadPoolTaskExecutor. The pool starts with zero threads and creates up to corePoolSize threads as tasks arrive. When core threads are busy, new tasks queue up to the queueCapacity. If the queue fills and maxPoolSize threads are busy, new tasks are rejected. The execution table traces each task submission, thread usage, and queue size. Key moments clarify lazy thread creation, queue filling, and task rejection. The quiz tests understanding of thread counts, queue behavior, and configuration effects.

Practice

1. What is the main purpose of configuring a custom thread pool in a Spring Boot application?

easy

A. To change the database connection settings

B. To control the number of threads used for asynchronous tasks

C. To modify the HTTP request timeout

D. To customize the logging format

Solution

1. Step 1: Understand thread pools in Spring Boot

   Thread pools manage how many threads run tasks concurrently, improving performance and resource use.

2. Step 2: Identify the role of custom thread pools

   Custom thread pools let you set limits on thread count and behavior for asynchronous processing.

3. Final Answer:

   To control the number of threads used for asynchronous tasks -> Option B

4. Quick Check:

   Thread pool purpose = control threads [OK]

Hint: Thread pools manage threads for async tasks [OK]

Common Mistakes:

• Confusing thread pool with database or HTTP settings
• Thinking thread pools affect logging
• Assuming thread pools are for UI rendering

2. Which of the following is the correct way to define a custom thread pool bean in Spring Boot using Java configuration?

easy

A. @Bean public Executor taskExecutor() { return Executors.newFixedThreadPool(5); }

B. @Bean public Executor taskExecutor() { return new ThreadPoolExecutor(); }

C. @Bean public Executor taskExecutor() { return new ScheduledThreadPoolExecutor(10); }

D. @Bean public Executor taskExecutor() { return new ThreadPoolTaskExecutor(); }

Solution

1. Step 1: Recall Spring Boot thread pool bean creation

   Spring Boot uses ThreadPoolTaskExecutor for custom thread pools, which integrates with Spring's task execution.

2. Step 2: Analyze options

   @Bean public Executor taskExecutor() { return new ThreadPoolTaskExecutor(); } correctly returns a new ThreadPoolTaskExecutor instance, which is the recommended way.

3. Final Answer:

   @Bean public Executor taskExecutor() { return new ThreadPoolTaskExecutor(); } -> Option D

4. Quick Check:

   Spring thread pool bean = ThreadPoolTaskExecutor [OK]

Hint: Use ThreadPoolTaskExecutor for Spring thread pools [OK]

Common Mistakes:

• Using Executors.newFixedThreadPool directly without Spring wrapper
• Trying to instantiate ThreadPoolExecutor without parameters
• Confusing scheduled thread pools with normal thread pools

3. Given this Spring Boot configuration snippet, what will be the maximum number of threads allowed in the pool?

@Bean
public ThreadPoolTaskExecutor taskExecutor() {
  ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
  executor.setCorePoolSize(3);
  executor.setMaxPoolSize(6);
  executor.setQueueCapacity(10);
  executor.initialize();
  return executor;
}

medium

A. 6

B. 3

C. 10

D. 13

Solution

1. Step 1: Understand core and max pool size

   Core pool size is minimum threads kept alive; max pool size is the maximum threads allowed.

2. Step 2: Identify maxPoolSize value

   The code sets maxPoolSize to 6, so the pool can grow up to 6 threads.

3. Final Answer:

   6 -> Option A

4. Quick Check:

   Max threads = maxPoolSize = 6 [OK]

Hint: Max threads = maxPoolSize property [OK]

Common Mistakes:

• Confusing queue capacity with max threads
• Thinking corePoolSize is max threads
• Adding corePoolSize and queueCapacity incorrectly

4. What is wrong with this custom thread pool configuration in Spring Boot?

@Bean
public ThreadPoolTaskExecutor taskExecutor() {
  ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
  executor.setCorePoolSize(5);
  executor.setMaxPoolSize(3);
  executor.setQueueCapacity(10);
  executor.initialize();
  return executor;
}

medium

A. Missing @EnableAsync annotation on configuration class

B. Queue capacity cannot be set in ThreadPoolTaskExecutor

C. Core pool size is greater than max pool size, which is invalid

D. ThreadPoolTaskExecutor cannot be returned as a bean

Solution

1. Step 1: Check core and max pool size relationship

   Core pool size must be less than or equal to max pool size; here core is 5 but max is 3, which is invalid.

2. Step 2: Validate other settings

   Queue capacity is valid; @EnableAsync is optional but recommended; returning ThreadPoolTaskExecutor bean is correct.

3. Final Answer:

   Core pool size is greater than max pool size, which is invalid -> Option C

4. Quick Check:

   Core pool ≤ max pool required [OK]

Hint: Core pool size must not exceed max pool size [OK]

Common Mistakes:

• Setting core pool size larger than max pool size
• Assuming queue capacity is mandatory to set
• Forgetting to add @EnableAsync (not always required)

5. You want to create a custom thread pool in Spring Boot that has a core pool size of 4, max pool size of 8, and a queue capacity of 20. You also want to set a thread name prefix "MyApp-" for easier debugging. Which of the following code snippets correctly implements this configuration?

hard

A. @Bean
public ThreadPoolTaskExecutor taskExecutor() {
ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
executor.setCorePoolSize(4);
executor.setMaxPoolSize(8);
executor.setQueueCapacity(20);
executor.setThreadNamePrefix("MyApp-");
executor.initialize();
return executor;
}

B. @Bean
public Executor taskExecutor() {
return Executors.newFixedThreadPool(8);
}

C. @Bean
public ThreadPoolTaskExecutor taskExecutor() {
ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
executor.setCorePoolSize(8);
executor.setMaxPoolSize(4);
executor.setQueueCapacity(20);
executor.setThreadNamePrefix("MyApp-");
executor.initialize();
return executor;
}

D. @Bean
public ThreadPoolTaskExecutor taskExecutor() {
ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
executor.setCorePoolSize(4);
executor.setMaxPoolSize(8);
executor.setQueueCapacity(20);
executor.setThreadNamePrefix("App-");
executor.initialize();
return executor;
}

Solution

1. Step 1: Verify core, max pool sizes and queue capacity

   Core pool size 4, max pool size 8, and queue capacity 20 match the requirement in @Bean public ThreadPoolTaskExecutor taskExecutor() { ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor(); executor.setCorePoolSize(4); executor.setMaxPoolSize(8); executor.setQueueCapacity(20); executor.setThreadNamePrefix("MyApp-"); executor.initialize(); return executor; }.

2. Step 2: Check thread name prefix correctness

   @Bean public ThreadPoolTaskExecutor taskExecutor() { ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor(); executor.setCorePoolSize(4); executor.setMaxPoolSize(8); executor.setQueueCapacity(20); executor.setThreadNamePrefix("MyApp-"); executor.initialize(); return executor; } sets thread name prefix to "MyApp-" exactly as requested.

3. Step 3: Validate other options

   @Bean public Executor taskExecutor() { return Executors.newFixedThreadPool(8); } uses fixed thread pool without prefix; @Bean public ThreadPoolTaskExecutor taskExecutor() { ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor(); executor.setCorePoolSize(8); executor.setMaxPoolSize(4); executor.setQueueCapacity(20); executor.setThreadNamePrefix("MyApp-"); executor.initialize(); return executor; } reverses core and max sizes (invalid); @Bean public ThreadPoolTaskExecutor taskExecutor() { ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor(); executor.setCorePoolSize(4); executor.setMaxPoolSize(8); executor.setQueueCapacity(20); executor.setThreadNamePrefix("App-"); executor.initialize(); return executor; } uses wrong prefix.

4. Final Answer:

   Option A code snippet correctly implements the required configuration -> Option A

5. Quick Check:

   Correct sizes and prefix = @Bean public ThreadPoolTaskExecutor taskExecutor() { ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor(); executor.setCorePoolSize(4); executor.setMaxPoolSize(8); executor.setQueueCapacity(20); executor.setThreadNamePrefix("MyApp-"); executor.initialize(); return executor; } [OK]

Hint: Match core, max sizes and prefix exactly [OK]

Common Mistakes:

• Swapping core and max pool sizes
• Using wrong thread name prefix
• Using fixed thread pool instead of ThreadPoolTaskExecutor