"Harvey, David " <[EMAIL PROTECTED]> wrote on 24/07/2006 02:50:17:
> Thanks for your comments, discussion. However, this occurs when
> caching is turned on, i.e.
> -Dorg.apache.tapestry.disable-caching=false.
>
> I sure hope there's a fix, I don't know if MaxPermSize can be made
> any larger in
L PROTECTED] On Behalf Of Jean-Eric
> Cuendet
> Sent: 22 July 2006 18:22
> To: Tapestry users
> Cc: Tapestry users;Tacos Developers
> Subject: Re: [Tacos-devel] PermGen space
>
> Hi all,
> This problem is very common with Tapestry applications. This is due to
> the fact
: [Tacos-devel] PermGen space
Hi all,
This problem is very common with Tapestry applications. This is due to
the fact that Tapestry uses cglib to generate classes at runtime.
Java uses a separate Heap space called "PermGenSpace" to put meta-data
about classes, which is never garbage collecte
Thanks for your comments, discussion. However, this occurs when caching is
turned on, i.e.
-Dorg.apache.tapestry.disable-caching=false.
I sure hope there's a fix, I don't know if MaxPermSize can be made any larger
in production and it sounds from your discussion that making it larger will
Hi all,
This problem is very common with Tapestry applications. This is due to
the fact that Tapestry uses cglib to generate classes at runtime.
Java uses a separate Heap space called "PermGenSpace" to put meta-data
about classes, which is never garbage collected (this is "normal" since
normally
Hello all,
We've been having occasional problems with PermGen out of space errors
thrown during the execution of our Tapestry application. We usually get
a stack trace with something about hivemind at the top (see below).
Then, of course, we have to restart our app server. Our environment is
