Because of the way that file system locking works on Windows
platforms, hot redeployment of a Web application on Windows can sometimes
fail. Hot redeployment may also fail when you stop or undeploy a Web
application on Windows. The problem can occur when you use the HQ user
interface or the
To resolve the problem:
file of the tc Runtime instance and set the following two attributes
<Context> element to
antiJARLocking: When set to
true, the tc Runtime classloader takes extra
measures to avoid JAR file locking when resources are accessed
inside JARs through URLs. This action affects the startup time of
applications, but is useful on platforms (such as Windows) or
configurations where file locking can occur.
antiResourceLocking: When set to
true, tc Runtime prevents any file locking.
This action affects startup time of applications significantly,
but allows full Web application hot redeploy on platforms (such as
Windows) or configurations where file locking can occur.
context.xml snippet shows how
to specify the attributes; only the relevant part of the file is
<Context antiJARLocking="true" antiResourceLocking="true"> <WatchedResource>...
Restart the tc Runtime instance for the change to take effect.
tc Runtime to copy files rather than read them in place. Also, if you try
to copy in a new
.jsp file directly, tc Runtime does
not pick it up.
If you prefer, you can set these two properties in the
context.xml file of the application itself rather than
context.xml file for the entire tc Runtime
For more information and warnings about configuring the
context.xml file, see The