[jboss-jira] [JBoss JIRA] (WFLY-6349) JMSXGroupId has no effect on JMSProducer
Jeff Mesnil (JIRA)
issues at jboss.org
Wed Mar 30 10:07:00 EDT 2016
[ https://issues.jboss.org/browse/WFLY-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183944#comment-13183944 ]
Jeff Mesnil commented on WFLY-6349:
-----------------------------------
You are right: there is indeed a bug in Artemis: https://issues.apache.org/jira/browse/ARTEMIS-462.
The workaround is to set the JMSXGroupID on the Message until Artemis fixes this bug.
Note that JMSXGroupSeq is an optional behaviour and your use case is valid. Messages must be grouped using JMSXGroupId regardless of the presence of the JMSXGroupSeq property
> JMSXGroupId has no effect on JMSProducer
> ----------------------------------------
>
> Key: WFLY-6349
> URL: https://issues.jboss.org/browse/WFLY-6349
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Harald Wellmann
> Assignee: Jeff Mesnil
> Fix For: 10.1.0.Final
>
>
> h3. Scenario
> I'm setting the {{JMSXGroupID}} on a {{JMSProducer}} to achieve message delivery in the correct order. The consumer is a message-driven bean.
> {code}
> JMSProducer producer = context.createProducer();
> producer = producer.setProperty("JMSXGroupID", "sequential");
> producer = producer.setProperty("foo", "bar");
> for (int i = 0; i < 50; i++) {
> msgNumber++;
> String text = "This is message " + msgNumber;
> producer.send(queue, text);
> }
> {code}
> h3. Expected Behaviour
> The messages are received in the correct order, the properties {{JMSXGroupID}} and {{foo}} are set on the receiver side.
> h3. Actual Behaviour
> The messages are received in random order. Property {{foo}} is set, but property {{JMSXGroupID}} is null on the receiver side.
> h3. Workaround
> Create a {{TextMessage}} and set the properties on the message, not on the producer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list