Repository navigation
Conversation
mattrpav
changed the title
…spatch PolicyEntry.useMessageGroups (default true). When false, Queue.assignMessageGroup returns immediately: no consumer is ever assigned a group, no ownership is recorded, JMSXGroupFirstForConsumer is never set, and a group's messages are dispatched across consumers like any other messages. Applied on configure and through the runtime policy update path (includedProperties "useMessageGroups"), and exposed on the queue MBean (isUseMessageGroups/setUseMessageGroups) for inspection and runtime toggling.
mattrpav
force-pushed
the
amq-policy-use-message-groups
branch
from
October 26, 2026 18:03
5ee8e85 to
3c92f6f
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
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.
PolicyEntry.useMessageGroups (default true). When false, Queue.assignMessageGroup returns immediately: no consumer is ever assigned a group, no ownership is recorded, JMSXGroupFirstForConsumer is never set, and a group's messages are dispatched across consumers like any other messages. Applied on configure and through the runtime policy update path (includedProperties "useMessageGroups").
Currently, there is not a well-documented way to disable message groups and prevent queue stalls and deadlocks that can arise from those messages -- specifically, when ActiveMQ is only being used as a transport or pass-through of messages.