Fix for SQSSessionCallbackScheduler zombie threads #48
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yeshodhan
changed the title
|
any news on this? |
|
can this be related to #108? |
|
@yeshodhan I took over this library and recently doing some clean-up. This PR LGTM, can you do a git pull and push another commit? And how to interpret the graph you posted? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
After checking for session.isRunning() and adding a timeout for callbackQueue.wait(), I was able to achieve the results as below:
I'm not sure if the timeout needs to be configured somewhere ?
Easiest way to reproduce the issue is to disconnect from internet and run the spring DefaultMessageListenerContainer.