[
https://issues.apache.org/activemq/browse/CAMEL-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Crickenberger updated CAMEL-315:
--------------------------------------
Attachment: camel-core.closeInputStreams.patch
camel-ftp.closeInputStreams.patch
Added patch for camel-ftp for FtpProducer and SftpProducer. Added patch for
camel-core, as it looks like UnmarshalProcessor might cause the same thing to
happen.
> Unclosed InputStreams cause FileConsumer to hang on Windows
> -----------------------------------------------------------
>
> Key: CAMEL-315
> URL: https://issues.apache.org/activemq/browse/CAMEL-315
> Project: Apache Camel
> Issue Type: Bug
> Reporter: Aaron Crickenberger
> Attachments: camel-core.closeInputStreams.patch,
> camel-ftp.closeInputStreams.patch
>
>
> FtpProducer/SftpProducer get their "In" Message bodies as InputStreams, which
> they then neglect to close. This appears to cause a problem in Windows where
> Files that are processed in this manner have an exclusive lock placed upon
> them.
> For more info, see this discussion thread:
> http://www.nabble.com/From-file-to-ftp-td14921828s22882.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.