There may be something that the RA is doing which triggers the broker to
select a new consumer for each message in the group. Ultimately message
grouping is designed to ensure that the messages are consumed sequentially
in order (i.e. not concurrently). Typically that's done by selecting a
single c
Thank you Betram for your comments. I will try to clarify inline.
> What observations are you making that lead you to this conclusion? Please be
> specific.
We kept record of the message groups used and the identity of the consumer (MDB
instance) handling the last message in each group and log
> As far as we can tell the attribute is ignored and messages with the same
group-id move from one consumer to the other.
What observations are you making that lead you to this conclusion? Please
be specific.
> Now I have read in the release notes for ActiveMQ 6.1 that issue
ENTMQ-261 has been re
Hello all,
We use Apache ActiveMQ Artemis Message Broker version 2.16.0 inside our Wildfly
server. We are trying to get message grouping working by setting the
JMSXGroupID attribute on messages that are being handled by various MDBs. As
far as we can tell the attribute is ignored and messages w
