archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Graham <chrisgw...@gmail.com>
Subject Re: Memory leak in Archiva 2.0.1
Date Wed, 30 Apr 2014 04:30:12 GMT
:)

I had 1.6G in the Spring DefaultListableBeanFactory. I've not checked it
with 2.0.1 yet, as it takes a few months to crash (for me).

-Chris



On Wed, Apr 30, 2014 at 2:12 AM, Sascha Vogt <sascha.vogt@gmail.com> wrote:

> Hi all,
>
> I think we found a memory leak.
>
> In a heap dump taken while Archiva was pretty busy doing GCs, we found
> DefaultArchivaConfiguration to be holding references to 10.000
> registryListeners (which in turn had Jackrabbit XASessionImpls) and
> occupied 84 of our 4GB heap.
>
> Is this related to the following comment we found:
>
> /**
> * A consumer of content (files) in the repository.
> *
> * olamy: TODO/FIXME we must review this api, in the current situation we
> use prototype beans rather than singletons
> * this is a bit memory consuming the better will be to ConsumerContext
> bean to transport repository context etc...
> */
> public interface RepositoryContentConsumer
>
> Will the registryListeners ever be cleaned up? Any ideas how to address
> that?
>
> Greetings
> -Sascha-
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message