Wrap ThreadPoolTaskScheduler with TaskSchedulerWrapper.
We now expose a wrapped ThreadPoolTaskScheduler to not expose the bean to the context directly to avoid interference with other components requiring a properly configured ThreadPoolTaskScheduler for e.g. AtAsync usage. We remove the risk of accidentally exhausting the pool and in consequence, ensuring the pool has sufficient capacity to handle Vault background jobs. Resolves gh-623.
This commit is contained in:
@@ -6,7 +6,7 @@ Mark Paluch;
|
||||
:self-docs-root: https://docs.spring.io/spring-vault/docs/{version}/
|
||||
:example-root: ../../../../spring-vault-core/src/test/java/org/springframework/vault/documentation
|
||||
|
||||
(C) 2016-2020 The original authors.
|
||||
(C) 2016-2021 The original authors.
|
||||
|
||||
NOTE: _Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically._
|
||||
|
||||
|
||||
@@ -11,6 +11,7 @@
|
||||
* Documentation of <<vault.core.secret-engines,how to use Vault secret backends>>.
|
||||
* Login credentials for Kubernetes and PCF authentication are reloaded for each login attempt.
|
||||
* `SecretLeaseContainer` publishes `SecretLeaseRotatedEvent` instead of `SecretLeaseExpiredEvent` and `SecretLeaseCreatedEvent` on successful secret rotation.
|
||||
* `AbstractVaultConfiguration.threadPoolTaskScheduler()` bean type changed to `TaskSchedulerWrapper` instead of `ThreadPoolTaskScheduler`.
|
||||
|
||||
[[new-features.2-2-0]]
|
||||
=== What's new in Spring Vault 2.2
|
||||
|
||||
Reference in New Issue
Block a user