Make a note of the problem described by JBPAPP-3133:

• Cause of Problem: Bug in JVM implementations [1,2,3] that leads to a JVM crash (SIGSEGV) when a zip file is accessed before and after it has been overwritten.

[1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6366468
[2] https://bugzilla.redhat.com/show_bug.cgi?id=466034
[3] http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=316

• Consequence of Problem: The JVM can crash when a incomplete deployment is overwritten by a new version of the deployment during hot deployment. So, for example, consider a deployment which contains a formatting error in a deployment descriptor. When deployed, the error is encountered and the deployment fails. If the erroneous deployment is replaced with a corrected version by copying over the old deployment, the JVM may crash during the hot deployment of the new version.

• Workaround: The issue can be avoided if one removes the old, incompletely deployed archive before copying the new, corrected deployment into the deploy directory