Ensure that cache monitor is shut down when appender is stopped #145
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.
@bluedenim Found one more leak after integrating the previous fix. The
TimePeriodBasedBufferMonitor
also creates an executor service that is not properly being shut down when the dynamically allocated appender is stopped. Simple fix is to move the shutdown call to the cache monitor into the same extracted method in the previous PR. The good news here is that the previous fix did address the leak of theLoggingEventCache-publish-thread
. Now, we see a leak of theTimePeriodBasedBufferMonitor-publish-trigger
, which this fix should address.