[
https://issues.apache.org/activemq/browse/CAMEL-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52958#action_52958
]
Dave Stanley commented on CAMEL-1849:
-------------------------------------
Given this stream is only created to hold the body of of http exception's,
another option might be to change the HttpOperationFailedException
implementation to use a string for the body rather than an InputStream.
This way the stream can be safely closed in HttpProducer.
In terms of the exception body itself, if its a large exception body the entire
body could be logged and then [optionally] truncated in the Exception object
itself if needed?
> CachedOutputStream not cleaning up tmp files when using file based caching
> --------------------------------------------------------------------------
>
> Key: CAMEL-1849
> URL: https://issues.apache.org/activemq/browse/CAMEL-1849
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core, camel-http
> Affects Versions: 1.6.1
> Environment: Camel 1.x branch. 2.0 branch also appears to have the
> same problem
> Reporter: Dave Stanley
> Assignee: Hadrian Zbarcea
> Fix For: 1.6.2
>
> Attachments: camel_1.x_patch.txt
>
>
> A recent feature of Camel's CachedOutputStream is to serialize any messages
> over 64k to disk. In some cases the *tmp message files are not being cleaned
> up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
