[ http://jira.jboss.com/jira/browse/JBMESSAGING-1149?page=comments#action_1... ] Tim Fox commented on JBMESSAGING-1149: -------------------------------------- Changes required to implement this are fairly simple. The new feature will work as follows: Deploy the queue/topic on all nodes of the cluster as clustered = "true" (since still need failover) and also set "disableRedistribution" (new attribute) to true. This will prevent messages being redistributed between nodes for that destination. Next, deploy a connection factory, set attribute "Singleton" = true (new attribute). This will ensure the connection factory only actually gets bound in JNDI on one node in the cluster at any one time. Deploy the connection factory on all nodes. Then just set MDB pool size to 1 (can use the Singleton MDB profile) and all messages sent to that queue/topic will be consumed on the same node. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1149?page=all ] Tim Fox updated JBMESSAGING-1149: --------------------------------- Fix Version/s: Unscheduled (was: 1.4.0.SP2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1149?page=all ] Tim Fox updated JBMESSAGING-1149: --------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewforum&f=153 Reverted for now. We need to think more carefully about how to do this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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. -- 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

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1149?page=com.atlassian.ji... ] Clebert Suconic updated JBMESSAGING-1149: ----------------------------------------- Fix Version/s: 2.0.0 (was: 2.0.0.beta4) -- 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