2012/11/15 Duc Trung TRAN :
> Konstantin,
>
> Does it means it's a bad thing to use jsp as templating inside a webapp?
It is bad thing to bundle Tomcat components inside web applications.
You should never do that. [1] should explain why.
[1] and [2] should explain why things are different between
Konstantin,
Does it means it's a bad thing to use jsp as templating inside a webapp?
And it's normal that it breaks *other* applications but not the application
itself? I would expect the opposite scenario.
Thanks and regards
Trung
2012/11/15 Konstantin Kolinko
> 2012/11/14 Christopher Schult
2012/11/14 Christopher Schultz :
>
>> Do you have any idea why old jasper-compiler (used inside an
>> application) provoke errors to other applications? Is it a bug? Or
>> is there some additional config to make it works?
>
> Oh, this breaks *other* applications? There may be some weirdness,
> here
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trung,
On 11/14/12 10:18 AM, Duc Trung TRAN wrote:
> We are trying to migrate Tomcat 5.5 to Tomcat 7. And We have
> issues in an old application which make use of JspC class. In fact,
> this application has an internal jsp templating and use JspC to
>
Chris,
>> As article says, container drops all reference to classloader during
>> web-app undeploy. This allows GC to remove classloader and free PermGen.
>> In our system, JSP deployed inside web-app without web-app
>> redeply. So references to ClassLoader aren't dropped.
>
>Aah, I didn't realiz
Nikita,
>> I read through your ClassLoader. It doesn't look like it will compile,
>
> Why? It were compiled and run on my PC.
Oh, sorry. The indentation was a little funny and I didn't see the
method signature for "private byte loadClassData(File f)". Never mind.
>> I'm not sure what your Class
Chris,
>>> If so, then you can't fix the
>>> problem by writing your own JSP compiler and/or ClassLoader.
>>
>> I guess loading each JSP class by separate classloader instance
>> will fix the problem. Classloader will be created when HTTP request
>> recived and no one reference on this classloader
Nikita,
>> If so, then you can't fix the
>> problem by writing your own JSP compiler and/or ClassLoader.
>
> I guess loading each JSP class by separate classloader instance
> will fix the problem. Classloader will be created when HTTP request
> recived and no one reference on this classloader
Chris,
>> I work on application which allows user to deploy/undeploy large
>> number of the JSP pages to AppServer (JBoss 4.03sp1 + Tomcat 5.5).
>> Standard Tomcat class loader caches classes for all deployed JSP
>> internally and never clean its cache. This brings JVM to PermGen
>> overflow e
Nikita,
> I work on application which allows user to deploy/undeploy large number of
> the JSP pages to AppServer (JBoss 4.03sp1 + Tomcat 5.5). Standard Tomcat
> class loader caches classes for all deployed JSP internally and never clean
> its cache. This brings JVM to PermGen overflow error after
10 matches
Mail list logo
