The first thing to make clear is what you mean by clustering ... If you just need load balancing, i guess you could do that using plain http or jms. You would achieve nearly the same thing by using jms binding endpoints on each of you jbi endpoint.
Note that using the clustering facilities provided by your J2EE container may be a good idea, though I have no idea what kind of features you will be able to leverage atm. However when you cluster a JBI endpoint, you may want an instance of the endpoint on one node being able to resume an exchange that has been initiated by the same JBI endpoint on another node in the cluster. This is much more complex, as it requires that the component's state for this exchange (if any) is also clustered, or that the component tell the NMR that there is no state to maintain (in such a case, the exchange can be easily resumed on another node). ServiceMix uses a specific property for that which is handled on the JMS / JCA flow. On 10/2/06, Jeffrey Puro <[EMAIL PROTECTED]> wrote:
I am looking for the best method for clustering ServiceMix within my company's Enterprise. It seems like there are potentially 2 ways of doing this. The first is to use the JMS Flow mechanism that is built into ServiceMix. I have not used this yet, but I'm sure it works just fine. The second approach is to re-use whatever clustering capabilities are already in my J2EE server. I guess it sort of depends on how I plan on deploying this application, standalone or within a J2EE server. So really there are 2 questions: 1) What is the best method of running ServiceMix in order to achieve high availability and reliable messaging? Standalone or within a J2EE app server? 2) If I deploy within a J2EE app server, what is the best way to cluster ServiceMix? Should I continue to use JMS Flow or should I just rely on the clustering capabilities of the J2EE app server? Regards, Jeff Puro This email (and any attachments) is intended only for the use of the individual or entity named above and may contain information that is privileged and confidential. If you are not the intended recipient, or have unauthorized access, you are hereby notified that copying, disseminating, distributing or taking any action in reliance on this email is strictly prohibited<br /> <br /> Opinions, conclusions and other information in this message that do not relate to the official business of our firm shall be understood as neither given nor endorsed by it.
-- Cheers, Guillaume Nodet
