You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Christopher Hammack <ch...@fadedsky.com> on 2008/12/02 17:13:33 UTC
Memory leak in FileConsumer in Camel 1.5.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.
Thanks.
--
View this message in context: http://www.nabble.com/Memory-leak-in-FileConsumer-in-Camel-1.5.0-tp20794405s22882p20794405.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Memory leak in FileConsumer in Camel 1.5.0
Posted by Christopher Hammack <ch...@fadedsky.com>.
Claus,
I applied changeset 722808 to my copy of 1.5.0 and it does appear to use
considerably less memory after one hour of operation.
Thanks,
-cnh
Claus Ibsen-2 wrote:
>
> Chris
>
> I have committed a quick fix for this in the 1.5.1-SNAPSHOT.
> http://activemq.apache.org/camel/download.html
>
> Do you mind testing it? Note that in Camel 2.0 we have refactored the
> file consumer so it should not consume all this memory.
>
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Tue, Dec 2, 2008 at 5:37 PM, Hadrian Zbarcea <hz...@gmail.com>
> wrote:
>> Many thanks for pointing this out. I created
>> https://issues.apache.org/activemq/browse/CAMEL-1138.
>>
>> Hadrian
>>
>> On Dec 2, 2008, at 11:13 AM, Christopher Hammack wrote:
>>
>>>
>>> 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.
>>>
>>> Thanks.
>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Memory-leak-in-FileConsumer-in-Camel-1.5.0-tp20794405s22882p20794405.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Memory-leak-in-FileConsumer-in-Camel-1.5.0-tp20794405s22882p20814803.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Memory leak in FileConsumer in Camel 1.5.0
Posted by Claus Ibsen <cl...@gmail.com>.
Chris
I have committed a quick fix for this in the 1.5.1-SNAPSHOT.
http://activemq.apache.org/camel/download.html
Do you mind testing it? Note that in Camel 2.0 we have refactored the
file consumer so it should not consume all this memory.
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Tue, Dec 2, 2008 at 5:37 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> Many thanks for pointing this out. I created
> https://issues.apache.org/activemq/browse/CAMEL-1138.
>
> Hadrian
>
> On Dec 2, 2008, at 11:13 AM, Christopher Hammack wrote:
>
>>
>> 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.
>>
>> Thanks.
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Memory-leak-in-FileConsumer-in-Camel-1.5.0-tp20794405s22882p20794405.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
Re: Memory leak in FileConsumer in Camel 1.5.0
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Many thanks for pointing this out. I created https://issues.apache.org/activemq/browse/CAMEL-1138
.
Hadrian
On Dec 2, 2008, at 11:13 AM, Christopher Hammack wrote:
>
> 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.
>
> Thanks.
>
>
> --
> View this message in context: http://www.nabble.com/Memory-leak-in-FileConsumer-in-Camel-1.5.0-tp20794405s22882p20794405.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>