[ https://issues.apache.org/jira/browse/ARTEMIS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-462. ------------------------------------ Resolution: Fixed Fix Version/s: 1.3.0 > JMSXGroupId is not taken into account when set on the JMSProducer > ----------------------------------------------------------------- > > Key: ARTEMIS-462 > URL: https://issues.apache.org/jira/browse/ARTEMIS-462 > Project: ActiveMQ Artemis > Issue Type: Bug > Affects Versions: 1.1.0 > Reporter: Jeff Mesnil > Assignee: Justin Bertram > Fix For: 1.3.0 > > > Use case: > * Set "JMSXGroupId" on the JMSProducer and send messages > Expected behaviour: > * a single consumer (in our case a MDB) should receive all messages serially > Actual behaviour: > * messages are consumed by different consumers > The issue occurs only if the JMSXGroupId is set on the JMSProducer. When it > is set on the Message itself, the behaviour is correct. > The issue occurs when the JMSProducer set its properties on the message to > send in ActiveMQJMSProducer#setProperties. > Properties are all set using ActiveMQMessage#setObjectProperty. However > JMSXGroupId is handled specifically in ActiveMQMessage#setStringProperty() to > translate it to the Artemis own's HDR_GROUP_ID. This special case is absent > from setObjectProperty and the underlying Artemis ClientMessage does not have > the HDR_GROUP_ID property set and messages will not be grouped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)