You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Angela <an...@iwes.fraunhofer.de> on 2015/03/19 14:01:30 UTC
Aggregator - Problem with accepting files for second time
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.
Re: Aggregator - Problem with accepting files for second time
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
You have noop=true, so camel wont pickup the same files again - its in
idempotent mode.
You can try setting the idempotent key to include the file size as shown on
http://camel.apache.org/file2
Then if the files are changed it should pickup them again.
On Thu, Mar 19, 2015 at 2:01 PM, Angela
<an...@iwes.fraunhofer.de> wrote:
> 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.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/