Swapped Pool Size to be managed in Spring Properties #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
You can validate the pool size being set by using the follow breakpoints.
TaskSchedulingConfigurations.TaskSchedulerBuilderConfiguration::taskSchedulerBuilder
sets the builder from the properties.TaskSchedulingConfigurations.TaskSchedulerConfiguration::taskScheduler
builds yourThreadPoolTaskScheduler
using that builder.A similar swap can be done for your
CaffeineCacheManager
, which you can dig into here. Which can be beneficial for testing where yourMockCacheManager
can instead just bespring.cache.type=SIMPLE