Hi, i've written following route:
<c:from uri="file://abc?noop=true&initialDelay=30000&include=....(grib?|md5)" /> <c:aggregate groupExchanges="true" completionSize="2"> <c:correlationExpression> <c:simple>${file:onlyname.noext}</c:simple> </c:correlationExpression> <c:process ref="checkMD5Processor" /> ...... </c:aggregate> For the first arriving of each file it works as expected. But if the same two files arriving again (for example xy.grib and xy.md5) the aggregation doesn't start for a long time (in our example the second processing starts after 2 days). Does anybody knows the reason and/or the aggregator options for stopping this behavior. Thanks, Angela -- View this message in context: http://camel.465427.n5.nabble.com/Aggregator-Problem-with-accepting-files-for-second-time-tp5764443.html Sent from the Camel - Users mailing list archive at Nabble.com.