Hi,There's well known problem Tomcat and classloaders not being garbage collected after succesive deploys. I know, it's not a Tomcat problem but java in general. But Tomcat admins face it often. It's very painful on Windows, because not unloaded classloader keeps locked jars, so hot redeploy is not possible (at least with struts + hibernate webapp).
I have to make a Tomcat setup for a client, who is not much 'IT aware' ;-) I modified global web.xml to turn off development mode, I modified global context.xml to turn on antiJARLocking and antiResourceLocking.
The effect is I can smoothly redeploy my webapp, no locking occurs. Tomcat docs say, that it impacts application startup. But is there any impact on later performance? The startup may by slow, it doesn't matter.
I noticed, that with such configuration Tomcat first: unpacks war to webapps directory, and second: copies all unpacked directory to its temp directory. Does it make sens to turn off unpackWars? What will be the impact on performance with unpackWars set to false?
-- Mikolaj Rydzewski <[EMAIL PROTECTED]>
smime.p7s
Description: S/MIME Cryptographic Signature
