tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikita Belov" <>
Subject RE: JSP class loader
Date Wed, 26 Jul 2006 10:38:32 GMT

>> 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 realize that you were doing this. So, you basically
>maintain your own versioning for each JSP? 

Yes. New JSP deployed to different directory.

>If I request that a JSP job
>be run several times, each run gets its own class compiled and loaded?

I think yes. Obsolete classes removed only on web-app undeploy.

>This seems a little kludgey. You are you using JSP as a batch processing

What do you mean "batch processing"?

>> I see, threre are two possible ways for now: modify jsp servlet as I
>> going to before or create web-app for each business process and redeploy
>> it when new JSP arrived.
>I realize that you are probably required to work within the boundaries
>of a pre-existing system, 

Our system is the platform for other applications (as Tomcat it-self). 
Therefore, it can't be "pre-existed".


To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message