Skip to content

Commit

Permalink
DOCS - Clarify that pool size properties are ignored with task executor
Browse files Browse the repository at this point in the history
spring-projects#39529

Signed-off-by: Jakob Wanger <[email protected]>
  • Loading branch information
wanger26 committed Feb 20, 2024
1 parent 4fd0e29 commit f14754e
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Shrinking of the pool is more aggressive as threads are reclaimed when they are

A scheduler can also be auto-configured if it needs to be associated with scheduled task execution (using `@EnableScheduling` for instance).
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.
Otherwise, it will be a `ThreadPoolTaskScheduler` with sensible defaults.
Otherwise, it will be a `ThreadPoolTaskScheduler` with sensible defaults. Note, the `SimpleAsyncTaskScheduler` will ignore any pool size properties.

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:

Expand Down

0 comments on commit f14754e

Please sign in to comment.