ActiveMQ / JMS has a built-in mechanism to ensure that messages that share a common header (namely the JMSXGroupID header) are always consumed by the same queue consumer when using a competing consumer pattern. Consumers of the queue do not fully correspond to the actual values โโof the header, since the guarantee of messages with a common header is performed on the server side, and not on the consumer side. For more details on how this works, see http://activemq.apache.org/message-groups.html .
Does it do something with AMQP or with something specific RabbitMQ?
source share