Henryk, that sounds like a limitation in the design of aggregators in Camel,
rather than a necessarily desirable end goal.
--
View this message in context:
http://camel.465427.n5.nabble.com/Aggregate-up-to-N-ASAP-tp5758134p5758312.html
Sent from the Camel - Users mailing list archive at Nabble.
Thanks. I'm not sure on whether the current design of the aggregator actually
allows for this though? I think the current design is "push" based: an
upstream processor "pushes" exchanges into the aggregator; the aggregator's
completion mechanism then decides whether to submit or not, yet.
I think
I understand how they work. These proposals don't resolve the problem. I only
want to take /whatever is already available on the SEDA/. I recognize that
this will take longer than 0ms, but the point is that I do not want to wait
for /any more/ messages to arrive once I've grabbed whatever is availa
t;Transacted Batch Consumers & Producers". I
>> haven't used this feature myself but I have just started to use the sjms
>> component since I prefer not using Spring.
>>
>> /Bengt
>>
>>
>> 2013/9/24 bacar
>>
>> > Hi,
>> >
Thanks - I'll try that!
--
View this message in context:
http://camel.465427.n5.nabble.com/Consuming-multiple-JMS-messages-in-one-single-transaction-tp5640489p5740558.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I need to do something very similar to this request from April 2012, ie
consume multiple JMS messages in a single transaction. Is the advice still
current?
Does the same also apply for the opposite, ie consuming a single message in
a transaction, and then writing multiple output messages in on
Yes, I considered this as a temporary workaround but it doesn't really suit
our case; optimistic locking ought to work well when you don't expect a lot
of contention; unfortunately I expect large batches of tens of thousands of
sequential messages that I expect to get batched together into small gr
Just to add yet another layer of clarity (I hope this is helping...)
lock.lock();
try {
doAggregation(key, copy);
} finally {
lock.unlock();
}
Taking a *very* simplistic view, doAggregation() does two things:
1.
