Polishing
This commit is contained in:
@@ -47660,12 +47660,11 @@ element.
|
||||
rejection-policy="CALLER_RUNS"/>
|
||||
----
|
||||
|
||||
|
||||
Finally, the `keep-alive` setting determines the time limit (in seconds) for which threads
|
||||
may remain idle before being terminated. If there are more than the core number of threads
|
||||
currently in the pool, after waiting this amount of time without processing a task, excess
|
||||
threads will be terminated. A time value of zero will cause excess threads to terminate
|
||||
immediately after executing tasks.
|
||||
threads will get terminated. A time value of zero will cause excess threads to terminate
|
||||
immediately after executing a task without remaining follow-up work in the task queue.
|
||||
|
||||
[source,xml,indent=0]
|
||||
[subs="verbatim,quotes"]
|
||||
@@ -47676,6 +47675,8 @@ immediately after executing tasks.
|
||||
keep-alive="120"/>
|
||||
----
|
||||
|
||||
|
||||
|
||||
[[scheduling-task-namespace-scheduled-tasks]]
|
||||
==== The 'scheduled-tasks' element
|
||||
The most powerful feature of Spring's task namespace is the support for configuring
|
||||
|
||||
Reference in New Issue
Block a user