[
https://issues.apache.org/activemq/browse/CAMEL-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2817.
--------------------------------
Fix Version/s: 2.4.0
Resolution: Fixed
trunk: 955126.
I found an issue and have fixed this. You are welcome to test with 2.4-SNAPSHOT
jars on your system.
The fix is in camel-core so you need to upgrade all Camel JARs to 2.4-SNAPSHOT
> renames (to .processed) are sometimes done even if the download failed.
> -----------------------------------------------------------------------
>
> Key: CAMEL-2817
> URL: https://issues.apache.org/activemq/browse/CAMEL-2817
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-ftp
> Affects Versions: 2.1.0
> Environment: linux, apache ftp server.
> Reporter: Karl Palsson
> Assignee: Claus Ibsen
> Fix For: 2.4.0
>
>
> I have an ftp consumer endpoint URI like:
> {{ftp://conaxt...@localhost:2121/autreq/ok?passiveMode=true&password=conaxTest&move=.processed&delay=5000}}
> From my ftp server logs, I can see files being downloaded, and then renamed...
> {quote}
> [org.apache.ftpserver.command.impl.RETR:pool-2-thread-56] - <File downloaded
> /autreq/ok/vp006331.emm>
> [org.apache.ftpserver.command.impl.RETR:pool-2-thread-56] - <File downloaded
> /autreq/ok/vp006332.emm>
> [org.apache.ftpserver.impl.DefaultFtpHandler:pool-2-thread-57] - <Session
> idle, closing>
> [org.apache.ftpserver.command.impl.RNTO:pool-2-thread-56] - <File rename from
> "/autreq/ok/vp006331.emm" to "/autreq/ok/.processed/vp006331.emm">
> [org.apache.ftpserver.command.impl.RNTO:pool-2-thread-54] - <File rename from
> "/autreq/ok/vp006332.emm" to "/autreq/ok/.processed/vp006332.emm">
> [org.apache.ftpserver.command.impl.RNTO:pool-2-thread-54] - <File rename from
> "/autreq/ok/vp006333.emm" to "/autreq/ok/.processed/vp006333.emm">
> {quote}
> Note, that vp006333.emm is renamed, but was never downloaded. There's no
> other mention of the file in my logs. On the camel ftp consumer side, I see
> that camel attempted to download the file, but ended up with a null...
> {quote}
> [is.vf.conan.conax.FileParser:Camel thread 7: seda://updateOk] - <handling:
> GenericFile[vp006331.emm]>
> [is.vf.conan.ConanCore:Camel thread 7: seda://updateOk] - <updating operation
> txid:006331 with the results: OK>
> [is.vf.conan.conax.FileParser:Camel thread 7: seda://updateOk] - <handling:
> GenericFile[vp006332.emm]>
> [is.vf.conan.ConanCore:Camel thread 7: seda://updateOk] - <updating operation
> txid:006332 with the results: OK>
> [is.vf.conan.conax.FileParser:Camel thread 7: seda://updateOk] - <handling:
> GenericFile[vp006333.emm]>
> [is.vf.conan.conax.FileParser:Camel thread 7: seda://updateOk] - <Requested
> parse of an empty file!>
> {quote}
> The "requested parse of an empty file" is logged when
> {{ex.getIn().getBody(String.class)}} is empty or blank for the file object.
> I had a look through the bugs fixed for 2.3.0, but I don't see anything that
> would be related to this at all.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
