[
https://issues.apache.org/jira/browse/CAMEL-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063337#comment-14063337
]
Claus Ibsen commented on CAMEL-7601:
------------------------------------
Just use maxMessagesPerPoll on the file consumer, and let it rollback if there
was a problem. Then you dont need any kind of redelivery and the files are
picked up in the order you want, eg if you do any kind of sorting.
The current code in camel-core works as designed. Redelivery is blocked by
default. And if you enable async, then redeliveries can happen out of order.
And please use the mailing list / user forum for the initial help, as we say
here
http://camel.apache.org/support
> maximumRedeliveries=-1 plus scheduledExecutorService=pool(1 thread) equals
> problem
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-7601
> URL: https://issues.apache.org/jira/browse/CAMEL-7601
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.12.1, 2.13.2
> Reporter: Andrzej Gdula
> Priority: Minor
>
> https://github.com/agdula/camel-test/blob/master/src/test/java/com/pb/psep/testbase/ThreadPoolTest.java
> Test that demonstrates a problem when
> onException(SomeException.class).maximumRedeliveries(-1)
> and
> scheduledExecutorService=poolOfThreads(X)
> When there are lots of routes using single threadPool and there happen to be
> more than X exceptions in X routes that will be redelivered forever
> then thread pool gets hogged and other routes are unable to process.
> Thread are stuck on
> org.apache.camel.processor.RedeliveryPolicy.sleep(RedeliveryPolicy.java:188)
> If camel instead of waiting would schedule retry then it probably would
> solve the problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
