AFAIK, JSP classes stick around as long as the parent classloader holds onto
it. So once the parent classloader is defererenced, all the classes in that
classloader can be garbage collected.
-Tim
Dale, Matt wrote:
Hi,
I have a question which may be a general java question but it relates to a
So it would require a context reload to free up the space used by JSPs as opposed to
just replacing all the JSPs?
Ta
Matt
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: 16 July 2004 16:10
To: Tomcat Users List
Subject: Re: JSPs - Permanent Generation
AFAIK, JSP
: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: 16 July 2004 16:10
To: Tomcat Users List
Subject: Re: JSPs - Permanent Generation
AFAIK, JSP classes stick around as long as the parent classloader holds onto
it. So once the parent classloader is defererenced, all the classes in that
classloader can
On Fri, Jul 16, 2004 at 11:34:19AM -0400, Tim Funk wrote:
: Nope. A new classloader (JasperLoader) is instaniated for every JSP page
: loaded. When the JSP is recompiled. A new JasperLoader is created.
: JasperLoader should only be loading that single JSP. Once the JSP is
: recompiled, the old
our problems were just that it wasnt big enough. I have now upped this 128MB so
will hopefully solve the problem.
Thanks
Matt
-Original Message-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: 16 July 2004 16:34
To: Tomcat Users List
Subject: Re: JSPs - Permanent Generation
Nope. A new
