[
https://issues.apache.org/activemq/browse/CAMEL-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47809#action_47809
]
Claus Ibsen commented on CAMEL-1138:
------------------------------------
These maps is part of some code logic to determine if the file has been changed
using timestamp and filesize checks. All this code has been @deprecated and
removed in 2.0.
It leads to unexpected behavior and is hard to test. And shouldn't generally be
used.
If you use file connectivity then you should either delete or move files after
they are processed and not keep then around.
As a fix for this in 1.5.1 I have added the LRUCache so the maps will contain
at most 1000 elements.
> Memory leak in FileConsumer
> ---------------------------
>
> Key: CAMEL-1138
> URL: https://issues.apache.org/activemq/browse/CAMEL-1138
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.5.0
> Reporter: Hadrian Zbarcea
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 1.5.1, 2.0.0
>
>
> Using a memory profiler, we've identified what appears to be a substantial
> memory leak in FileConsumer in Camel 1.5.0. It appears that the noopMap is
> constantly having items added to it, but nothing performs a remove on it when
> the file is consumed. This causes a very large amount of string data to be
> accumulated in the heap. In our application, this was a leak of several
> hundred megabytes and is a showstopper. Considering the apparent severity
> of this issue, it would really be nice if a fix could be incorporated into a
> 1.5.1 version.
> http://www.nabble.com/Memory-leak-in-FileConsumer-in-Camel-1.5.0-td20794405s22882.html#a20794405
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
