Table of Contents
pages about debugging configuration, troubleshooting warnings in the logs, etc
A Zip exception occurs when Jetty rereads a Jar or WAR file.
The JVM maintains a cache of zip file indexes, and does not support hot replacement of zip files. Thus if you redeploy a web application using the same WAR or Jar files, exceptions occur when Jetty rereads the jars. See Oracle Bug 4774421 for more information.
The remedy is to avoid hot replacing Jar or WAR files, which can be difficult if you are using the hot Context Provider. You can use the following techniques to reduce exposure to this issue:
WEB-INF/classes
directory rather than as a Jar file
under WEB-INF/lib
.Be aware that any of the techniques listed above that involve copying part or all of the webapp will probably not avoid the zip file problem if you are using a work directory (which avoids re-extraction on start/stop of a context or container).
If you have problems with Windows file-locking preventing static file editing (such as JSP or HTML), use the WebAppContext.setCopyWebDir(true) option.