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());