Description

If you request precompilation of JSPs when you deploy an application
on Windows, later attempts to undeploy that application or to redeploy it
(or any application with the same module ID) will not work as expected. The
problem is that JSP precompilation opens JAR files in your application but
does not close them, and Windows prevents the undeployment from deleting those
files or the redeployment from overwriting them.

Note that undeployment succeeds to a point, in that the application
is logically removed from the Application Server. Also note that no error
message is returned by the asadmin utility, but the application's
directory and the locked jar files remain on the server. The server's log
file will contain messages describing the failure to delete the files and
the application's directory.

Attempts to redeploy the application after undeploying fail because
the server tries to remove the existing files and directory, and these attempts
also fail. This can happen if you try to deploy any application that uses
the same module ID as the originally deployed application, because the server
uses the module ID in choosing a directory name to hold the application's
files.

Attempts to redeploy the application without undeploying it first will
fail for the same reasons.