local or HA is a configuration issue. There's nothing to stop you deploying JBossMQ twice.
I'd like to see the HA choice more fine grained at the queue/topic subscription level, but I can only repeat what I've said many times before... Explain how you elect one server to be the transaction controller for each session and how you coordinate the disparate work efficiently without turning your whole cluster into a single threaded machine. Or similarly, how to make a contested queue work across a cluster with an efficient distributed lock (if such a thing even exists) or equivalent mechanism. Selectors on queues are usually bad. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844815#3844815 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844815 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
