archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sascha Vogt <sascha.v...@gmail.com>
Subject Re: Memory leak in Archiva 2.0.1
Date Tue, 13 May 2014 16:58:47 GMT
I can :)

just upgraded... Let's see where this is tomorrow after a full day of
builds and deployments *hehe*.

Thanks again for fixing so quickly.

Greetings
-Sascha-

Am 13.05.2014 09:14, schrieb Olivier Lamy:
> Ok I pushed a fix in master.
> Let me know if you can test it :-)
> 
> Thanks!!
> Olivier
> 
> On 12 May 2014 18:53, Sascha Vogt <sascha.vogt@gmail.com> wrote:
>> Hi,
>>
>> Am 12.05.2014 05:20, schrieb Olivier Lamy:
>>> Hi,
>>> Just to correctly understand.
>>>  org.apache.archiva.consumers.core.MetadataUpdaterConsumer         |  45.052
>>> This mean the jvm retains 45052 instances of this class?
>> Yes, and today we're at 59k ;) So growth over the weekend was slow (so
>> it probably has to do something with uploads to Archiva).
>>
>>> Are they attached to any other object(s)?
>>
>> If I read the heapdump correctly, then I think they are entries in the
>> registryListener set of DefaultArchivaConfiguration.
>> Just verified via Debugger, the registryListener set contains 130k
>> entries (59k MetadataUpdteConsumer + 59k ArtifactMissingChecksumsConsumer)
>>
>> Greetings
>> -Sascha-
>>
> 
> 
> 


Mime
View raw message