Sorry, in this case MyProcessor is done in under 1 second, so it is well within the visibility timeout
On 8/5/15 5:26 AM, Claus Ibsen wrote: > How long time does it take to process the message on the seda route? > eg how long time does MyProcessor take? > > Though I think the problem is that maybe Amazon SQS is not thread safe > when one thread consumes a message, and another thread marks the > message as deleted. If that is the case we need to deny handover in > the delete task. > > > > > > On Wed, Aug 5, 2015 at 10:01 AM, Claus Ibsen <[email protected]> wrote: >> What version of Camel do you use? And have you tried to upgrade and use >> latest? >> >> On Thu, Jul 30, 2015 at 10:32 PM, bitsof info <[email protected]> wrote: >>> I have a route like this, the messages are sent to MyProcessor but are >>> NOT deleted from SQS, they go invisible for 30 seconds, but then >>> re-appear in SQS as available messages. >>> >>> from("aws-sqs://myqueue?amazonSQSClient=#myclientbean&waitTimeSeconds=20&maxMessagesPerPoll=10&visibilityTimeout=30&deleteAfterRead=true") >>> .to("seda:inbound-queue?waitForTaskToComplete=Never&concurrentConsumers=1") >>> .process(new MyProcessor()); >>> >>> >>> IF I delete the SEDA route statement, it works as expected >>> >>> >>> from("aws-sqs://myqueue?amazonSQSClient=#myclientbean&waitTimeSeconds=20&maxMessagesPerPoll=10&visibilityTimeout=30&deleteAfterRead=true") >>> // COMMENT OUT AND SQS messages get deleted >>> .to("seda:inbound-queue?waitForTaskToComplete=Never&concurrentConsumers=1") >>> .process(new MyProcessor()); >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2nd edition: http://www.manning.com/ibsen2 > >
