<route>
<from
uri="jms:topic:LoggingTopic?maxConcurrentConsumers=5"/>
<to uri="bean:msgParser"/>
<to uri="bean:log4jBean"/>
</route>
I am getting a weird behavior. When I send three messages to the logging
topic having the maxConcurrentConsumers set to 5, the first message is
logged once, the second message is processed twice, the third message three
times.
All subsequent messages are sent multiple times at the exact time and
processed multiple times.
RequestA
ResponseA
RequestB
RequestB
ResponseB
ReponseB
RequestC
RequestC
RequestC
ResponseC
ResponseC
ResponseC
James.Strachan wrote:
>
> 2008/10/22 selezovikj <[EMAIL PROTECTED]>:
>>
>> <route>
>> <from uri="jms:topic:LoggingTopic"/>
>> <to uri="bean:msgParser?concurrentConsumers=5"/>
>> </route>
>>
>> Camel is complaining about the msgParser bean, saying that the
>> concurrentConsumers propety is not defined.
>
> the concurrentConsumers property is defined on the JMS endpoint BTW
>
>
>> I was wondering what is the correct way to set the number of
>> concurrentConsumers and maxConcurrentConsumers for a bean ?
>
> Its the consuming (from) endpoint which defines concurrency.
>
>
>> When I use the @Service annotation of
>> org.springframework.stereotype.Service
>> package to denote a bean inside Java, it cannot set concurrentConsumers.
>> The
>> only thing it provides is the value of the bean.
>
> You can set it on the @MessageDriven annotation URI
> http://activemq.apache.org/camel/pojo-consuming.html
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
>
--
View this message in context:
http://www.nabble.com/Bean-properties%3A-concurrentConsumers-problem-tp20113967s22882p20127586.html
Sent from the Camel - Users mailing list archive at Nabble.com.
