[
https://issues.apache.org/jira/browse/QPID-7937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188294#comment-16188294
]
ASF subversion and git services commented on QPID-7937:
-------------------------------------------------------
Commit b9409b6c6414c7bbd1a251e637953150264a9836 in qpid-broker-j's branch
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=b9409b6 ]
QPID-7937: [Java Broker] Rename Queue#messageGroupKey to
#messageGroupKeyOverride to emphasise that the attribute is now optional
* Corresponding UI, converter and upgrader changes.
* On update/converter remove messageGroupKey of JMSXGroupId so that default is
used
* Changed MessageGroupQueueTest to avoid using AMQSession.
> [Java Broker] [AMQP1.0] Message grouping feature does not utilise group-id
> from the message properties
> ------------------------------------------------------------------------------------------------------
>
> Key: QPID-7937
> URL: https://issues.apache.org/jira/browse/QPID-7937
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0, qpid-java-6.1
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> The AMQP 1.0 specification provides a {{group-id}} field within the immutable
> message properties to pass the message grouping key. When enabled, the
> message grouping feature should be utilising this field the key for message
> grouping purposes. Currently the implementation looks for an application
> header (behaviour inherited from the older protocols).
> As discussed here:
> http://qpid.2158936.n2.nabble.com/Consumer-affinity-JMSXGroupID-AMQP-1-0-tc7667309.html
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
