ARTEMIS-6203 make MQTT resiliency soak tests more robust - #6651
Merged
Conversation
There is another race in the soak test which focuses on resiliency for MQTT subscribers. After the subscription queue message count reaches 0 the PUBREC DuplicateIDCache may still hold entries because the core message is acknowledged when the broker receives the PUBREC while the cache entry isn't removed until the broker receives the PUBCOMP one round-trip later. It's possible the test will verify the cache size during this window and fail. The fix is simply to use Wait to verify the cache size. Co-Authored-By: Claude <noreply@anthropic.com>
jbertram
force-pushed
the
ARTEMIS-6203
branch
from
September 2, 2026 15:53
69768ab to
83f5c86
Compare
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
1 participant
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 is another race in the soak test which focuses on resiliency for MQTT subscribers. After the subscription queue message count reaches 0 the PUBREC DuplicateIDCache may still hold entries because the core message is acknowledged when the broker receives the PUBREC while the cache entry isn't removed until the broker receives the PUBCOMP one round-trip later. It's possible the test will verify the cache size during this window and fail.
The fix is simply to use Wait to verify the cache size.