Introduce mechanism to interrupt TrackingEventProcessor
worker threads
#2041
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.
This pull request adjusts the
TrackingEventProcessor
to introduce a solution to interrupt worker threads.It does so by adjusting the
WorkerLauncher
andTrackingSegmentWorker
Runnable
implementations intoWorker
implementations.The
Worker
interface, in turn, extendsRunnable
, and provides some flexibility to store and identify threads.This change stores every
Thread
constructed by theThreadFactory
in aMap
.This map is traversed on the private
awaitTermination
method, upon which it invokesjoin
for every thread present.Axon invokes the
join
method with a so-calledworkerTerminationTimeout
, configurable through theTrackingEventProcessorConfiguration
if necessary.Introducing this functionality has the effect that the
TrackingEventProcessor
no longer blocks an application shut down when theeventAvailabilityTimeout
exceeds the configured application shut down timeout.That makes this pull request is a follow-up from the discussions in issue #1981.