Could it be that, redeploying the application, JBoss creates a new
associated classloader, without releasing old classes and thus filling
up the memory space?
Ivano Pagano
Jason Dyer wrote:
I can't find the link right now, but I remember reading that when you load a
class, it gets stored in PermGen memory. The problem is that (apparently and
AFAICR) when a new version of a class is loaded, the old version is never
released from PermGen (Permanent Generation memory...)
This was specifically blamed on the JVM, and not a Tomcat bug. The fact that
it seems to happen with JBoss as well would tend to support that assertion.
-Jason
On Wednesday 25 January 2006 10:52, Sergiy Kyrylkov wrote:
Here is more
http://wiki.jboss.org/wiki/Wiki.jsp?page=OutOfMemoryExceptions
Jason, what makes you think it is a JVM issue?
Sergiy
-----Original Message-----
From: Jason Dyer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 25, 2006 5:44 PM
To: Tapestry users
Subject: Re: OutOfMemoryError
I had the same problem with tomcat. You can delay it by increasing
permanent
memory to the JVM, but the only real fix seems to be restarting on
deploy...
Apparently this is a JVM issue, not particular to any app server.
On Wednesday 25 January 2006 10:38, Cliff Zhao wrote:
After several times redeploy my war file in JBoss 4.0.3SP1, I get this
error: java.lang.OutOfMemoryError: PermGen space
Any advice?
Thanks.
--
Immortality consists largely of boredom.
-- Zefrem Cochrane, "Metamorphosis", stardate 3219.8
--------------
Jason Dyer
BlueTarp Financial, inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]