This all just extends the time until this error happens.
The only thing that really helps is enabling caching.
Cheers,
Markus
> There was an earlier tip on this list about increasing the size of the
> PermGen space. I use this in my JAVA_OPTS on my development machine (where
> I do lots of redeploying) and don't get OOME's any more.
>
> -Xms256m -Xmx256m -XX:MaxNewSize=256m -XX:MaxPermSize=256m
>
>
>
> ----- Original Message -----
> From: "Martin Strand" <[EMAIL PROTECTED]>
> To: <tapestry-user@jakarta.apache.org>
> Sent: Monday, November 28, 2005 10:24 AM
> Subject: java.lang.OutOfMemoryError: PermGen space
>
>
> > I keep getting this error from Tomcat:
> >
> > java.lang.OutOfMemoryError: PermGen space
> >
> > It seems to happen randomly. I read this article on TSS:
> > http://theserverside.com/news/thread.tss?thread_id=36743
> > "The permanent generation is special because it holds meta-data describing
> > user classes (classes that are not part of the Java language)."
> > As I understand it, the article implies that this error can occur when you
> > use a large number of classes. I've got less than 50 classes right now for
> > all components, pages and business logic but I'm still getting that error.
> >
> > Perhaps this PermGen space error is because of a large number of enhanced
> > classes? Or perhaps "hot code replace" leaves a number of old replaced
> > classes hogging the PermGen space?
> > Anybody else experiencing this?
> >
> > Martin
--
Markus Eberle
TNG Technology Consulting
[EMAIL PROTECTED]
http://www.tngtech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
