You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/12/02 19:16:05 UTC
[jira] Commented: (CAMEL-1138) Memory leak in FileConsumer
[ https://issues.apache.org/activemq/browse/CAMEL-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47793#action_47793 ]
Claus Ibsen commented on CAMEL-1138:
------------------------------------
This is *fixed in 2.0* as we have removed all this troublesome code.
For 1.5.1 I suggest to replace the noopMap with the LRUCahce Map so it keeps up till 1000 files and nothing more.
> 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
> 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.