[
https://issues.apache.org/activemq/browse/CAMEL-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47834#action_47834
]
Hadrian Zbarcea commented on CAMEL-1138:
----------------------------------------
I think so. It actually solves the leak problem.
The side effect is that if a file is not moved/renamed after 1000 other
entries/files it will disappear from the lru cache and look new again and get
reprocessed, which may also lead to an infinite loop (that would make another
one of those 1000+ files new/out of cache, and so on). However I don't think
this scenario is a valid one as it has other flaws, such as the fact that the
state is lost after a camel restart, so files would get processed again in that
case too (a comment in the code mentions that, actually).
I would add a warn in the wiki that not renaming/moving files is a dangerous
scenario and should not be used.
> 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.
