Thanks James for that precision. I have another question although. You said
Message Groups only applies to queues. Is that a part of JMS specification or just the way ActiveMQ handles the need of JMSXGroupID upon "TOPICS"? I went through the web and found nothing about that. Anyhow, thanks alot for your post. TIA, Harry 2007/4/19, James Strachan <[EMAIL PROTECTED]>:
On 4/19/07, Harry Co <[EMAIL PROTECTED]> wrote: > Hi all, > > > > I'm just trying to evaluate the JMSXGroupID functionality in ActiveMQ 4.0.2. > > But seems to not been working as described on activeMQ page ( > http://activemq.apache.org/message-groups.html). > This page says : > > When a message is being dispatched to a consumer, the JMSXGroupID is > > checked. If one is present then the broker checks to see if a consumer owns > > that message group. (Since there could be a massive number of individual > > message groups we use hash buckets rather than the actual JMSXGroupID > > string). > > > > If no consumer is associated with a message group a consumer is chosen. > > That JMS MessageConsumer will receive all further messages with the same > > JMSXGroupID value until > > > > - the consumer closes (or the client which created the consumer dies > > etc) > > - someone closes the message group by sending a message with a > > JMSXGroupSeq value of zero (see below for more details) > > > > So I assume (*correct me I'm wrong*): > > - if I have two consumers on the same topic, Message Groups only applies to queues. If you want message group functionality (sticky load balancing) then you need to use Virtual Destinations (which basically means consumers use queues).. http://activemq.apache.org/virtual-destinations.html -- James ------- http://radio.weblogs.com/0112098/
