up to well over 400 megs. our live servers have never gotten an
> > outta memory with caching on in the last two years, which makes me happy.
> >
> > evan
> > - Original Message -
> > From: "Norman Franke" <[EMAIL PROTECTED]>
> > To: &quo
rvers have never gotten an
outta memory with caching on in the last two years, which makes me happy.
evan
- Original Message -
From: "Norman Franke" <[EMAIL PROTECTED]>
To: "Tapestry users"
Sent: Thursday, June 28, 2007 12:25 PM
Subject: Re: OutOfMemoryError after
ay, June 28, 2007 12:25 PM
Subject: Re: OutOfMemoryError after serving N pages
I get this if I disable caching after a while. However, I have not seen it
with caching enabled.
-Norman
On Jun 28, 2007, at 11:47 AM, Evan Rawson - Work wrote:
what application host are you using. cuz i know in to
. i dont
know if this is some how related. but the only way to fix it is to
shut down and start tomcat back up.
evan
- Original Message - From: "Thomas Wiz" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 28, 2007 3:40 AM
Subject: Re: OutOfMemoryError after serving N p
s Wiz" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 28, 2007 3:40 AM
Subject: Re: OutOfMemoryError after serving N pages
Arjan Verstoep wrote:
I'm building an application with the Tapestry 4.0.2 framework, which
manages my music-collection. I'm getting OutOfMemoryErrors
Arjan Verstoep wrote:
>
> I'm building an application with the Tapestry 4.0.2 framework, which
> manages my music-collection. I'm getting OutOfMemoryErrors since I've
> created a small ajax-ish component that refreshes every 10 seconds to
> show the song that is currently playing. A piece of
May the sone property abstract. You are clearing it inside
finishLoad() which means, even with caching enabled, the song (and the
presumably Hibernate session that it was obtained from) is retained
needlessly between requests.
Most likely culprit is caching disabled, which leaks some memory
rela
ng, but just visually
looking at the state of the heaps during a load test can be quite
helpful.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 22 February 2007 13:22
> To: users@tapestry.apache.org
> Subject: RE: OutOfMemoryError after servi
7 13:22
> To: users@tapestry.apache.org
> Subject: RE: OutOfMemoryError after serving N pages
>
> Yeah, that is more sinister.
>
> Try dropping a lambdaprobe.war in your container and watching
> what happens to your app as you serve up N pages.
>
> It isn't as detai
ur
runtime environment and any resource constraints you may unknowingly
have.
http://www.lambdaprobe.org/d/index.htm
Tom
-Original Message-
From: Arjan Verstoep [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 8:15 AM
To: Tapestry users
Subject: Re: OutOfMemoryError after servi
[EMAIL PROTECTED] wrote:
We had the same thing, and in our case it was related to a small PermGen
Space setting in our Tomcat container.
My understanding of the Sun JVM is that it partitions up its allocated
memory into heap, perm gen, etc. chunks and that the Perm Gen space is
where all "meta d
We had the same thing, and in our case it was related to a small PermGen
Space setting in our Tomcat container.
My understanding of the Sun JVM is that it partitions up its allocated
memory into heap, perm gen, etc. chunks and that the Perm Gen space is
where all "meta data" about classes gets sto
12 matches
Mail list logo
