I'm not 100% on this, so someone correct me if I'm wrong.
* concurrentConsumers should only be set on the "from" part of a route.
using a queue in the "to" part of a route is not actually going to consume
any messages.
* You probably should not use concurrentConsumers at all with a topic. A
topic will route a copy of each message it receives to every consumer
attached to it. So if you have something like:
from("activemq:topic:topicName?concurrentConsumers=5").to("activemq:queue:queueName");
You will get 5 copies of each message sent to the topic placed on the
queue.
Travis
You probably do not want to use Concurrent Consumers on a topic. In
that scenario, each consumer will get a copy of each message sent to the
topic. Topics do not care if
On Wed, Jun 29, 2011 at 12:50 PM, rogelio_sevilla1 <
[email protected]> wrote:
> thanks for the answer Mr. Pham, I've commented my "concurrent configs" on
> my
> spring file and I've done it the way you propose:
>
>
> from("activemq:topic:xmlOrders").to("activemq:accounting?concurrentConsumers=5");
>
>
> Thanks for the advice. However, the activemq:accounting queue is still
> getting the message more than once, is this the normal behavior of the
> concurrentConsumers config???
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/concurrentConsumers-basic-question-tp4535789p4535904.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
