AER-4181 Fix taskmanager to handle RabbitMQ blocking on memory limit trigger#111
Merged
Hilbrand merged 3 commits intoaerius:mainfrom Feb 26, 2026
Merged
AER-4181 Fix taskmanager to handle RabbitMQ blocking on memory limit trigger#111Hilbrand merged 3 commits intoaerius:mainfrom
Hilbrand merged 3 commits intoaerius:mainfrom
Conversation
…trigger When RabbitMQ runs out of memory it will temporary block tasks on the queue. The taskmanager will than get disconnected. It will handle this, but it didn't update this correctly in the load statistics. As a result the taskmanager reported it was busy while it wasn't actually. This will result in few to none new tasks being put on the queue. The fix here is a change in the QueueWatchDog. That class now does the actually watching and calls reset to all relevant processes when a watch dog situation appears. Added unit test to test reset conditions in the different classes. Also update to use the latest aerius parent root pom (to also get ride of junit startup issues in Eclipse).
BertScholten
approved these changes
Jan 13, 2026
source/taskmanager/src/main/java/nl/aerius/taskmanager/adaptor/WorkerProducer.java
Outdated
Show resolved
Hide resolved
source/taskmanager/src/main/java/nl/aerius/taskmanager/domain/QueueWatchDog.java
Outdated
Show resolved
Hide resolved
Member
|
Would it be also helpful to detect blocked connections and try to handle them gracefully? ( https://www.rabbitmq.com/docs/connection-blocked ) |
BertScholten
approved these changes
Jan 14, 2026
source/taskmanager/src/main/java/nl/aerius/taskmanager/domain/QueueWatchDogListener.java
Outdated
Show resolved
Hide resolved
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
When RabbitMQ runs out of memory it will temporary block tasks on the queue. The taskmanager will than get disconnected. It will handle this, but it didn't update this correctly in the load statistics. As a result the taskmanager reported it was busy while it wasn't actually. This will result in few to none new tasks being put on the queue.
The fix here is a change in the QueueWatchDog. That class now does the actually watching and calls reset to all relevant processes when a watch dog situation appears. Added unit test to test reset conditions in the different classes.
Also update to use the latest aerius parent root pom (to also get ride of junit startup issues in Eclipse).