We are evaluating usage of message groups on ActiveMQ 5.5.1 using JDBC based Master/Slave configuration, with 1 queue and 8 consumers. What we are seeing is that if the queue is flooded with messages (we tried in the range of 20K) belonging to one group in short time-span and then add messages belonging to different groups, the messages belonging to different groups get processed serially instead of going to different consumer. We are using simpleMessageGroupMapFactory policy as our Message group Ids can have any long number. Is this is a known issue that is fixed in any subsequent release?, also, the message-group to consumer assignments , are they persisted in DB too? .. else how will the assignment get carried over to the slave broker when master goes down?
would appreciate any pointers in this. -- View this message in context: http://activemq.2283324.n4.nabble.com/Message-group-not-working-when-first-group-has-large-number-of-messages-tp4672269.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
