Re: Setting renameUsingCopy=true twice sets it to false!

[Andrea Cosentino]

Can you try with a newer version? Camel 2.15 is not released anymore.

Il giorno gio 23 mag 2019 alle ore 12:11 Hildegard Meier <daku8...@gmx.de>
ha scritto:

> Apache Camel 2.15.6
>
> Hi, the following Camel XML route honours renameUsingCopy=true, which is
> set once:
>
> <from
> uri="file:/edidaten/edi-smtpdak/ezv?delay=60000&amp;recursive=true&amp;startingDirectoryMustExist=false&amp;move=/edidaten/save/${date:now:yyyyMMdd}/edi-smtpdak/ezv/${in.header.CamelFileRelativePath}&amp;directoryMustExist=false&amp;autoCreate=false&amp;sortBy=file:modified&amp;exclude=^\..*&amp;readLock=markerFile&amp;renameUsingCopy=true&amp;backoffMultiplier=5&amp;backoffIdleThreshold=0&amp;backoffErrorThreshold=1"/>
>
> File processing speed is fast.
>
> But setting renameUsingCopy=true a second time afterwards, it seems that
> it sets renameUsingCopy=false, at least it makes the processing very slow
> (1-2 seconds) for each file, and I think that is caused by trying to move
> each file after processing, which fails because the "move" folder is on a
> separate filesystem, and then falls back to copy+delete, so setting
> renameUsingCopy=true is needed to make processing faster.
>
> Here the not-working (slow processing) URI. The only change is a inserted
> &renameUsingCopy=true after the move= parameter, so renameUsingCopy=true is
> given twice:
>
> <from
> uri="file:/edidaten/edi-smtpdak/ezv?delay=60000&amp;recursive=true&amp;startingDirectoryMustExist=false&amp;move=/edidaten/save/${date:now:yyyyMMdd}/edi-smtpdak/ezv/${in.header.CamelFileRelativePath}&amp;renameUsingCopy=true&amp;directoryMustExist=false&amp;autoCreate=false&amp;sortBy=file:modified&amp;exclude=^\..*&amp;readLock=markerFile&amp;renameUsingCopy=true&amp;backoffMultiplier=5&amp;backoffIdleThreshold=0&amp;backoffErrorThreshold=1"/>
>
> So, it looks like setting renameUsingCopy=true twice sets it to false!
> Should be easy to reproduce.
>