Hi all,
I have a global question about Camel behaviour. To be 'clear' as much as
possible I give an example :
Suppose the following route (in Spring config file):
<route>
<from uri="jms:queue:A">
<multicast>
<to uri=" jms:queue:B">
<to uri=" jms:queue:C">
</multicast>
</route>
<route>
<from uri="jms:queue:B">
<process ref="processor1">
</route>
<route>
<from uri=" jms:queue:C">
<to ref=" processor2">
</route>
Message content, Consumer and provider behaviour are not important for my
question.
My question is about the number of instance of processor1 and processor2
Camel or Spring will construct.
Is this number of instance depends on the value of "concurrentConsumer"
which can be specify to queue B and queue C ?
Thanks in advance for your answer.
Mta38
--
View this message in context:
http://www.nabble.com/Camel-and--object-memory-management-tp20697304s22882p20697304.html
Sent from the Camel - Users mailing list archive at Nabble.com.
