[ 
https://issues.apache.org/activemq/browse/CAMEL-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46518#action_46518
 ] 

Claus Ibsen commented on CAMEL-980:
-----------------------------------

Christian when I run your sample using camel 1.4.0 and drop first the ok and 
then the error file I get:

C:\cameltest>dir /s /b
C:\cameltest\in
C:\cameltest\ok
C:\cameltest\error
C:\cameltest\ok\shiporder_ok.xml
C:\cameltest\ok\shiporder_error.xml
C:\cameltest\error\shiporder_error.xml

There is no files in the in folder that is locked etc. However you get the 
error files *twice* and as it's in the ok folder *and* the error folder. We 
might consider the *moveNamePrefix* option to only work if the processing was a 
success (no exceptions). 

> File component - can not delete consumed file when processing failed (look 
> into real cause)
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-980
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-980
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Critical
>             Fix For: 1.5.0
>
>         Attachments: CamelExampleFileJaxb.zip
>
>
> See nabble:
> http://www.nabble.com/Problem-with-FileEndpoint-td19940096s22882.html
> *Workaround*
> Use .convertBodyTo(String.class) in the route so the file is read into 
> memory, and the java.io.File handler shouldn't be open/locked when camel 
> attempts to delete it after wards.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to