activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chir...@apache.org
Subject svn commit: r1423015 - /activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md
Date Mon, 17 Dec 2012 16:47:24 GMT
Author: chirino
Date: Mon Dec 17 16:47:23 2012
New Revision: 1423015

URL: http://svn.apache.org/viewvc?rev=1423015&view=rev
Log:
Fixing up APLO-280: Clarification about message groups

Modified:
    activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md

Modified: activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md
URL: http://svn.apache.org/viewvc/activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md?rev=1423015&r1=1423014&r2=1423015&view=diff
==============================================================================
--- activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md (original)
+++ activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md Mon Dec
17 16:47:23 2012
@@ -560,9 +560,8 @@ Message Groups are an enhancement to the
 Message Groups are logically like a parallel Exclusive Consumer. Rather 
 than all messages going to a single consumer, the stomp `message_group` header
 is used to define which message group the message belongs to. The Message Group feature
-then ensures that all messages for the same message group will be sent to the same 
-consumer - while that consumer stays alive. As soon as the consumer dies another 
-will be chosen.
+then ensures that all messages for the same message group will be sent to only 1 consumer

+at time.
 
 Another way of explaining Message Groups is that it provides sticky load balancing 
 of messages across consumers; where the message group value is kinda like a HTTP 
@@ -577,9 +576,9 @@ Here is an example message with the mess
     PO145
     ^@
 
-The broker uses consistent hashing to map message groups to consumers.  When you another
+The broker uses consistent hashing to map message groups to consumers.  When you add another
 subscription to a queue, the broker will first wait for messages sent to previous subscriptions
-to be processed and then the broker rebalances the message groups across consumers.
+to be processed and then the broker rebalances the message groups across the attached consumers.
 
 ### Temporary Destinations
 



Mime
View raw message