I have the same issue.
There are some temporary files that aren't deleted.
This an example of my code:
private class ProcessorSend implements Processor {
public void process(Exchange exchange) throws Exception {
//... some operations
String myEndpoint =
Hi Jason,
I just went though the HttpProducer code, and found if you don't close
the input stream from the message body, the temp file will never be
cleaned unless the camel application exits.
The CachedOutputSteam will not be closed when the exchange of the
HttpProducer oncomplicated, that
Hi
I have created a ticket to track this
https://issues.apache.org/jira/browse/CAMEL-4098
On Sat, Jun 11, 2011 at 8:58 AM, Claus Ibsen wrote:
> On Fri, Jun 10, 2011 at 9:43 PM, Jason Burkhardt wrote:
>> I dug into this a little further, here's the underlying behavior of the
>> HttpProducer:
>>
On Fri, Jun 10, 2011 at 9:43 PM, Jason Burkhardt wrote:
> I dug into this a little further, here's the underlying behavior of the
> HttpProducer:
> The method doExtractResponseBodyAsStream in HttpProducer ends up creating a
> CachedOutputStream based on the server response. This ends up creating
I dug into this a little further, here's the underlying behavior of the
HttpProducer:
The method doExtractResponseBodyAsStream in HttpProducer ends up creating a
CachedOutputStream based on the server response. This ends up creating a
cos* temp file in java.io.tmpdir+/camel-tmp.
These files are on
Hate to dredge up an old thread but I'm seeing this same behavior in 2.6.
Note: I am not calling stop or anything. This route processes a message
from JMS, calls http, processes the result and publishes it to JMS again.
This ends up writing tmp files with the soap response to
/tmp/camel-tmp-wha
Hi
Try sending plain txt mails (eg turn off HTML mails) that should work
much better with the mailing list.
I cannot reproduce the issue with stop on Camel trunk. I added some
unit tests to camel-jetty to simulate what you are doing and it works
fine.
The tmp files is always deleted.
On Mon, Ap
Thanks. Can you post the route with the stop that fails deleting the tmp
file?
And if possible feel free to create a JIRA ticket about this issue
http://camel.apache.org/support
-
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davscla
Can you try with a later release such as 2.6 or 2.7. The tmp files is deleted
using an oncompletion on the Exchange so it ought to be deleted regardless
if you are using stop or not. But that change may have been done in a later
Camel release than you use. I can't remember.
-
Claus Ibsen
-
