JAR locking in Tomcat web apps

david.matheson

Hi, all.  A common problem with undeploying web applications while Tomcat is running is that JARs in WEB-INF/lib get locked and mess things up.  A common solution to this is to use antiJARLocking="true" in the context.xml file of the web app, but this doesn't seem to help with dfc.jar.  Adding antiResourceLocking="true" seems to also cause problems when redeploying WDK apps (dam.war, in my case), I think because of the volume of JARs in the directory.

Has anyone else had these kinds of issues?  Is there any way to deploy dam.war without shutting down my Tomcat instance on Windows machines?

RalfKahrl

On the initialization of dfc some background threads (resource housekeeping...) are started.

I faced the same issue that these background threads are not stopped properly if you undeploy your webapp-context. I don't know if this is tomcat specific or not, but this may be the cause of your problem.