On Fri, Nov 12, 2010 at 9:12 AM, waterback <mart...@innoq.com> wrote: > > Hi Claus, > > maybe i didn't make myself clear enough... > The WMQ-Queue is rightfully configured for single-consumer only (this is > done in WebSphere MQ Message Broker), there should be only one consumer at > any time.... > > My Camel-App is destined to be installed in a WebSphere-Cluster (with 2 > servers). > With some trick i'll try to make sure that the route that consumes from this > queue is at least and at most started on one of both servers only. > > I understand what you suggest with "multipleconsumers=true", but where > should i put it, because the jms-component doesn't allow this argument? >
On the endpoint as it ought to support it. At least try it out first. > btw: Thanx... > > Martin > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Connect-with-WebSphere-MQ-Single-Consumer-allowed-tp3260184p3261601.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
