ith this CloudWatch component?
>
> At this moment such a component would be very useful for me :)
>
> Cheers
> Bilgin
>
> On 20 March 2012 23:54, dacc <[hidden email]> wrote:
>
>> Hello All,
>>
>> I'm considering adding a CloudWatch capability to
I'm trying to consume multiple exchanges from an SQS endpoint with autoack
disabled, but SqsConsumer blocks on completion of the first one that
arrives. I could have each of my workers poll SQS separately, but this will
increase the number of requests by a factor of the number of workers, which
do
Hey Claus,
Thanks for your reply.
SQS doesn't guarantee FIFO, so consumers already have to handle things being
out-of-order:
http://aws.amazon.com/sqs/faqs/#Does_Amazon_SQS_provide_first_in_first_out_FIFO_access_to_messages
Based on GenericFileConsumer, perhaps this is a better patch:
https://
Hello All,
I'm considering adding a CloudWatch capability to the AWS component. Does
this sound useful and/or is someone already working on it?
I'm writing an event-driven application that responds to changing metric
values in CloudWatch, and I'd like to use the same Akka/Camel message
pipeline
Ok, I made a ticket below:
https://issues.apache.org/jira/browse/CAMEL-5113
- D
--
View this message in context:
http://camel.465427.n5.nabble.com/Better-Way-to-Achieve-Parallel-Processing-of-SQS-Messages-tp5578135p5590255.html
Sent from the Camel - Users mailing list archive at Nabble.com.
