[
https://jira.jboss.org/jira/browse/JBMESSAGING-1149?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1149:
--------------------------------------
For JBM 2.0 this is a bit different.
The real requirement here can be solved by cluster wide message grouping.
With message groups, if you specify the message group group header, then all messages with
that same value of that header will be processed by the same consumer - this effectively
gives you a singleton consumer.
Normal message grouping only works on one node only, but we can extend it to always route
a message to the same consumer on a particular node irrespective of where the message was
sent from.
This can be done by setting up a message flow, which routes the message to a node based on
a hash of the message group header. Each node will evaluate the hash the same, so all will
send it to the same node. Once arrived on that node normal message grouping will occur.
Singleton consumer on queue/topic
---------------------------------
Key: JBMESSAGING-1149
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1149
Project: JBoss Messaging
Issue Type: Task
Affects Versions: 1.4.0.SP1
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 2.0.0 Beta
A last minute requirement came up from the AS team (Carlo and Bill DeCoste).
JBoss MQ uses HA singleton to provide a singleton consumer on a queue/topic. If that node
fails, the consumer should failover onto another single node.
Currently this isn't supported in JBM.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira