[jira] [Commented] (ARTEMIS-462) JMSXGroupId is not taken into account when set on the JMSProducer

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218896#comment-15218896 ] 

ASF GitHub Bot commented on ARTEMIS-462:
----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/433

    ARTEMIS-462 JMSXGroupID on JMS 2 producer

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-462

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/433.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #433
    
----
commit 2048198101a2e138ae568904b631dc38279119ea
Author: jbertram <jb...@apache.org>
Date:   2016-03-30T21:23:38Z

    ARTEMIS-462 JMSXGroupID on JMS 2 producer

----


> 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
>
> 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)