Skip to content

Commit 35e2a12

Browse files
wanger26mhalbritter
authored andcommitted
Clarify that pool size properties are ignored with task executor
Signed-off-by: Jakob Wanger <jakobwanger@gmail.com> See gh-39629
1 parent 86910b2 commit 35e2a12

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/task-execution-and-scheduling.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Shrinking of the pool is more aggressive as threads are reclaimed when they are
3838

3939
A scheduler can also be auto-configured if it needs to be associated with scheduled task execution (using `@EnableScheduling` for instance).
4040
When virtual threads are enabled (using Java 21+ and configprop:spring.threads.virtual.enabled[] set to `true`) this will be a `SimpleAsyncTaskScheduler` that uses virtual threads.
41-
Otherwise, it will be a `ThreadPoolTaskScheduler` with sensible defaults.
41+
Otherwise, it will be a `ThreadPoolTaskScheduler` with sensible defaults. Note, the `SimpleAsyncTaskScheduler` will ignore any pool size properties.
4242

4343
The `ThreadPoolTaskScheduler` uses one thread by default and its settings can be fine-tuned using the `spring.task.scheduling` namespace, as shown in the following example:
4444

0 commit comments

Comments
 (0)