Support spring 6.1.x lifecycle changes/late-shutdown for pubsub publisher scheduler #2738
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.
There has been a significant revision of
ThreadPoolTaskScheduler/Executor
lifecycle capabilities as part of the spring-6.1.x release. It includes a concurrently managed stop phase forThreadPoolTaskScheduler/Executor
, favouring early soft shutdown. As a result, theThreadPoolTaskScheduler
, which is used for pubsub publishing, now shuts down immediately onContextClosedEvent
, thereby rejecting any further task submissions (#2721).This PR aims to retain the default behavior of spring-6.1.x but provides config options to leverage the
lateShutdown
of the underlyingThreadPoolTaskScheduler
, such as:spring.cloud.gcp.pubsub.publisher.executor-accept-tasks-after-context-close=true
.References: