Message Grouping Not Respected When Using JMSXGroupID

[patrick-brielmayer]

We are experiencing issues with IBM MQ message grouping. Specifically, when we set the JMSXGroupID property on our messages, the messages do not arrive in the correct sequential order.

Expected Behavior:
When JMSXGroupID is used, messages sharing the same group ID should be delivered in the correct order, maintaining the sequence they were sent in. With multiple consumers (concurrency set to 10), messages from the same group should be directed to the same session/consumer, preserving their order.

Actual Behavior:
Messages are not delivered in the correct sequence, resulting in out-of-order message consumption within the same group.

Additional Information:

• We tested the same setup with ActiveMQ, and it correctly maintains the message sequence as intended.
• In our scenario, we would expect IBM MQ to route all messages with the same JMSXGroupID to the same session to preserve ordering.
• Environment details:
  • Java Version: 17
  • Spring Version: 3.4.0
  • mq-jms-spring-boot-starter: 3.3.5

Here is an example project that demonstrates the issue: https://github.com/patrick-brielmayer/ibm-mq-message-groups

[ibmmqmet]

Tying groups to a single consumer is an ActiveMQ extension of an optional feature beyond the required JMS specification.

See https://integration-development.ideas.ibm.com/ideas/MESNS-I-123 which is an enhancement request for IBM MQ. You can vote/comment on that. It's not something that can be handled through this repo.