[
https://issues.apache.org/jira/browse/AMQ-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064352#comment-15064352
]
Tim Bain commented on AMQ-5545:
-------------------------------
This is not a bug. Electing to use message groups is an explicit choice to
give up in-order dispatch for messages that are in the group compared with
messages that are either not in a group at all or are in another group.
Dispatch will be in-order for all messages within a single group (or for
messages that have no group), but there are no mechanisms provided or implied
for delaying dispatch/consumption of messages that are not in a given group
because an earlier message that's in the group has not yet been
dispatched/consumed.
Recommending re-closing. Abhinav, leave it closed this time around.
> Message order is not preserved across multiple consumers
> --------------------------------------------------------
>
> Key: AMQ-5545
> URL: https://issues.apache.org/jira/browse/AMQ-5545
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.0
> Environment: The issue is seen on both Linux and Windows.
> Reporter: Abhinav Sarkari
>
> There are multiple producers sending messages to a queue. There are multiple
> consumers on this queue.
> I want the consumers to pick messages in the same order as they have been
> send by the producers.
> The problem with using message group
> (http://activemq.apache.org/message-groups.html) is that only one consumer
> can consume these messages at a time. I want all the consumers on the queue
> to be actively picking the messages.
> In other words, is it possible to have multiple concurrent consumers being
> part of the message group?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
