L.S., The best option in your case would be to just use the JMS BC to put the message in the queue from ServiceMix and let the other servers read them off the queue again. By the way, you are aware that ActiveMQ is embedded inside ServiceMix, so there's not even a real need to set up a separate broker.
The JMS Flow is basically about clustering JBI containers, so if you are not doing that the plain JMS BC will work out fine for you. Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/2/18 mindy99 <[email protected]>: > > I am new to ServiceMix and am still in the knowledge gathering phase. I'm > trying to get my head around what kind of routing I should use for my needs. > I will have multiple physical servers supplying a service and am trying to > figure out the best approach using ServiceMix. I don't plan to cluster > ServiceMix itself, however. > > I want to use a persistent queue and have the various instances of the > services take items off the queue as they become available to process the > next item. Therefore, round robin doesn't really work. So, is the best > option to use a JMS BC and have my physical services just use JMS to pull > items off the queue or do I use a separate BC for each service and use some > kind of intelligent routing from within ServiceMix. (to accomplish the > latter, would that necessarily require the use of a JMS flow as opposed to > SEDA?) > > Thanks for any insight anyone can provide. > > -- Mindy > -- > View this message in context: > http://www.nabble.com/Routing-advice-tp22087549p22087549.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > >
