Sounds like you shouldn't be using ServiceMix in the first place. are you aware of Mule and Camel? These projects are more like what you describe. Servicemix solves communication between components on a higher level (JBI).
Geert. > > I read this whole thread, and based in my own experience, I wanted to ask > this to the OP poster: > > - Do you really need to cluster the endpoints? > > I ask this, because to be able to cluster the endpoints, you get stuck > with > JBI endpoints and the nmr. On the other hand, if you cluster the brokers > only, you can put queues on the key points you want to cluster and achieve > a > similar effect. The advantage of this approach is: > > - You don't need to use the nmr - you can use normal camel routes; > - You are not stuck with JBI - you can use osgi endpoints; > - You can pass java objects directly through the endpoints; no need to be > marshaling/unmarshaling xml documents to use on your code; > > You can achieve this by making something like: > > ENDPOINTA - QUEUE1 - ENDPOINTB - ENDPOINTC - QUEUE2 ..... etc > > messages will jump between brokers (same effect as clustered endpoints) > whenever you add a queue to the route. > > > -- > View this message in context: > http://old.nabble.com/Servicemix-4.2-clustering-issues.-tp28729394p28777441.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > > >
