When using concurrentConsumers with topics the ballpark changes as with topics each consumer gets a copy.
How is you JMS configuration. To avoid duplicates with topics you need to configure it a bit different. Cant quite remember. The people at the FUSE MQ forum might remember this better than I.
See the wiki page:
Could be that you need to tweak the consumerType option.
I think this is expected behaviour as a Topic is used (each concurrent consumer is effectively a subscriber to the topic). If you want to do loadbalancing, then you could switch to using a queue:
or alternatively maybe use a seda component in the middle:
Edited by: dstanley on Mar 27, 2009 4:26 PM
ok makes sense. the documentation for camel didn't provide these details.
the seda will work for now.
One thing I just realized is that the concurrentConsumers option for the seda component is only in Camel 1.6.1/2.0. You might need to use a snapshot for now until the next Fuse MR 1.x release to be able to use this feature of the seda component.
Yeah I noticed this as well. Unfortunately the 1.6.1 snapshot isn't available from their website at the moment.
I will eventually move to 2.0 but not at the current time.