> I want to use Camel to make a procedure test to an application. The test
> program must have configurable number of simultaneous threads.
> I have find this example:
> rom("activemq:queue:SOMETHING").pool(5 [min], 15 [max]).process(new
> How i can implement this solution using Spring?
> There is another way?
Hi Paul, only consumer components that support aync processing will be
able to leverage the async processing that the thread() call does.
Since the whole async processing model is new and optional.. not all
the existing components have been 'upgraded' to take advantage of it.
And the JMS component one of these guys that is still not taking
advantage of the async processing model.
So what happens is that the jms consumer delivers a message to the
processing route, but it does so synchronously. It will wait for the
exchange to be fully processed, even it's getting processed by a
thread from thread pool. Since it's waiting, it will not deliver
anymore messages until that thread from the thread pool is done
processing the exchange. This is why you only see 1 message getting
processed at a time.
One way to get around this would be to setup routes that look like:
The seda component does implement an async consumer. The one down
side to note is that message will be removed from the jms queue once
the message is delivered to the seda:a endpoint. It does not wait for
the message to get delivered to queue b before acking that it was
I think there is a bug in the Spring implementation.
I have tried your solution in JavaDSL and it worked, but in Spring the problem remains the same.
For now i will use JavaDSL but this is not a solution because i want to change some configurations without have to compile the code.
> Thanks Hiram.
> I think there is a bug in the Spring implementation.
> I have tried your solution in JavaDSL and it worked, but in Spring the
> problem remains the same.
> For now i will use JavaDSL but this is not a solution because i want to
> change some configurations without have to compile the code.
> If anyone find a solution, post it please.
> Paulo Ramos
> View this message in context:
> http://www.nabble.com/Processor-thread-pool-tf4627377s22882.html#a13290313 > Sent from the Camel - Users mailing list archive at Nabble.com.