Tim Bain wrote > Are all messages being immediately consumed, or is there a backlog of > messages for a given message group when you close the message group? I > would expect the message group to be closed immediately when the message > with NMSXGroupSeg=-1 is sent (not when it is consumed), so if there is a > backlog I would expect the new consumer to start processing with the next > undispatched message (which would be in the 200s), even if the old > consumer > is still processing its current message plus the one in its prefetch > buffer.
Yes, there are a backlog messages even after a group is closed. I thought that until a group is not closed (until message with NMSXGroupSeg=-1 is not processed and committed) it belongs to only one consumer. By the way, does NMSXGroupSeg needs to be in order or the NMSXGroupSeg order does not have any impact on processing? What about the situation when current NMSXGroupSeg has max value and next one has 1 (starting from scratch)? Tim Bain wrote > Why are you closing the message group? Seems like you could avoid the > whole problem just by doing that... What I'm trying to achieve is to periodically rebalance message groups along currently connected consumers (number of consumers can vary from time to time). I want to avoid the situation when new consumers are idle because all groups are processed by other consumers. I also need to keep the order of messages within group. Is there a better way to do it? Disconnect all consumers and reconnect? Thank you, -- View this message in context: http://activemq.2283324.n4.nabble.com/NMSXGroupID-problem-two-different-consumers-received-message-for-one-group-tp4705096p4705111.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
