jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Perez" <mper...@gmail.com>
Subject Re: memory profiling of jackrabbit
Date Sat, 16 Jun 2007 06:30:27 GMT
Hi Togeir,

Seeing a constant increase in the size of your old generation does not mean
necessarely that there is a memory problem. It can be some tolerable
background activity that moves references to the old gen.

I would take a look to the old generation size but only after major garbage
collections. If that size does continuously increase after major GCs then
you have a problem.


On 6/15/07, Torgeir Veimo <torgeir@pobox.com> wrote:
> Have anyone done any memory profiling of jackrabbit 1.3?
> In my webapp, I see the size of "CMs Old Gen" memory increase over time
> when there are no requests coming in, and I don't have any other components
> running background processes like jackrabbit does.
> My repository uses derby persistence and blobs in the filesystem.
> I'm including a screenshot of jconsole. Memory usage increases until the
> application just freezes with out of memory errors.
> --
> Torgeir Veimo
> torgeir@pobox.com

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