I'm using Tomcat 5.5.12 and I get this one or two times a day.
Disabling the cache should make Tapestry create a new class for each
page/component on each request, right? Perhaps old, unused enhanced
classes aren't properly removed from the PermGen space and that's why this
problem appears. If so, it would disappear if I just enable caching again.
I'm seeing this problem in my development environment (where caching is
disabled). Anyway, that's all speculation since I don't really know how
the details about class enhancement and PermGen space.
Martin
On Mon, 28 Nov 2005 16:24:15 +0100, Pedro Abelleira Seco <[EMAIL PROTECTED]>
wrote:
Yes, it's caused by class enhancement. You have to restart tomcat from
time to time to avoid it. _And_ don't disable tapestry caching in
production.
Pedro
El Lun, 28-11-2005 a las 16:24 +0100, Martin Strand escribió:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
