Browse Source

Merge pull request #39629 from wanger26

* pr/39629:
  Polish "Clarify that pool size properties are ignored with task executor"
  Clarify that pool size properties are ignored with task executor

Closes gh-39629
pull/39675/head
Moritz Halbritter 2 years ago
parent
commit
3668c5445c
  1. 6
      spring-boot-project/spring-boot-docs/src/docs/asciidoc/features/task-execution-and-scheduling.adoc

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

@ -37,9 +37,11 @@ This changes the thread pool to use a bounded queue so that when the queue is fu @@ -37,9 +37,11 @@ This changes the thread pool to use a bounded queue so that when the queue is fu
Shrinking of the pool is more aggressive as threads are reclaimed when they are idle for 10 seconds (rather than 60 seconds by default).
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.
If 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.
This `SimpleAsyncTaskScheduler` will ignore any pooling related properties.
If virtual threads are not enabled, it will be a `ThreadPoolTaskScheduler` with sensible defaults.
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:
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]

Loading…
Cancel
Save