Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=Vblu1+rTELRtxjLmppxjMqitutDei9AAbqvO1OhsHrghoLZVspSjd8zf0/Guj02lHwMKncMmt/OQV6jP55baTGFuL7N4vGBdYKSxNS3vg7iM5jlh5YcITkezfBSVHa9gpsvjhTdXPF3Y1ONzsQH+nT0VrOoJqHBxJ0p+jkArwHA=;
Date: Mon, 17 Mar 2008 17:50:58 -0700 (PDT)
From: footh <footh@yahoo.com>
Subject: Re: Javaflow - major memory issue
To: users@cocoon.apache.org
In-Reply-To: <47DEC9CD.80303@agssa.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <587883.96126.qm@web57901.mail.re3.yahoo.com>

Thanks for all the replies.  I did some more digging
into the profiling data.  It turns out that the
ContinuationsManagerImpl is at the top of the object
path of the byte arrays where 
org.apache.cocoon.environment.util.BufferedOutputStream
is the actual parent of the arrays.

Looking down the path, I can see the TreeSet and
SortedSet that is mentioned in cocoon-2109.  I would
say this issue is a likely cause for the memory
ballooning.

The load tester is simulating 5 users staggered 10
seconds apart and only hitting a couple very simple
pages.  Yet within 15 minutes, the Tomcat memory use
approaches 1GB.  After stopping the load tester and
examining the memory, I did notice in the profiler
that the byte arrays eventually cleaned up.  However,
looking at the Task Manger (using Windows), Tomcat was
still holding the full amount of memory from when I
stopped the load tester, ie. it didn't go down when
the  byte arrays cleaned up.

I suppose the next step is to try the patch provided
in  2109.  Any other suggestions?


--- Antonio Gallardo <agallardo@agssa.net> wrote:

> Hi,
> 
> Could it be this
> https://issues.apache.org/jira/browse/COCOON-2109 ?
> 
> Best Regards,
> 
> Antonio Gallardo.
> 
> Torsten Curdt escribi�:
> > I would have a look into the continuation
> management infrastructure in 
> > cocoon and then start digging from there. I am
> wondering if limiting 
> > and expiring the continuations works well enough
> for you. (It was on 
> > my TODO to improve this part in cocoon - but I
> never got around to it 
> > and moved on)
> >
> > cheers
> > -- 
> > Torsten
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail:
> users-help@cocoon.apache.org
> 
> 


      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org