You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Aaron Crickenberger (JIRA)" <ji...@apache.org> on 2008/02/01 02:03:35 UTC

[jira] Created: (CAMEL-315) Unclosed InputStreams cause FileConsumer to hang on Windows

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


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.


[jira] Assigned: (CAMEL-315) Unclosed InputStreams cause FileConsumer to hang on Windows

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea reassigned CAMEL-315:
-------------------------------------

    Assignee: Hadrian Zbarcea

> 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
>            Assignee: Hadrian Zbarcea
>         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.


[jira] Commented: (CAMEL-315) Unclosed InputStreams cause FileConsumer to hang on Windows

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41214#action_41214 ] 

Claus Ibsen commented on CAMEL-315:
-----------------------------------

Could there be other parts in Camel that have forgotten this?

> 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
>            Assignee: Hadrian Zbarcea
>         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.


[jira] Resolved: (CAMEL-315) Unclosed InputStreams cause FileConsumer to hang on Windows

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea resolved CAMEL-315.
-----------------------------------

    Fix Version/s: 1.3.0
       Resolution: Fixed

Applied with thanks!

> 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
>            Assignee: Hadrian Zbarcea
>             Fix For: 1.3.0
>
>         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.


[jira] Updated: (CAMEL-315) Unclosed InputStreams cause FileConsumer to hang on Windows

Posted by "Aaron Crickenberger (JIRA)" <ji...@apache.org>.
     [ 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.