Hi,
it's not the HTTP producer endpoint that keeps retrying the message. That
endpoint just fails and then the processing is complete. However this means
that the file consumer in your route does not delete or move the file, so it's
still there and the processing starts again with the next poll
For troubleshooting purposes, I split the route into 2, one with just sending
HTTP message and another one doing reading from file + transformations. When I
call the HTTP part only, it does try only once, like you said.
But when I run the whole route from the file: point, if exception happens
d
Hello,
You shouldn't need to set the max retry count to 0 as it is the default.
If that is the full log I suspect that is one try, try enabling debug
logging or checking the Web servers access togs to confirm. The first two
are info then the error stating it tried once. Exhausted after delivery
a
