SUN.ZIP.DISABLEMEMORYMAPPING__ Open Source Project (open

Sometimes you can cause JVM crash If you modify the jar file that the JVM is load. The stacktrace occurs when the Java.util.zip.ZipFile.getEntry ().

There are three possible scenarios here:
1. While a class was in the use it is dynamically reloaded from a jar file.
2. While a jar file is being accessed by the class loader, the jar file is being modified.
3. A Jarfile which was bigger than 4GB is accessed (applies to Java 6 and earlier only)

The solution is to make sure that the jar file is not updated or modified by other programs while the JVM is loading the jar file. The JVM then introduced a new property sun.zip.disableMemoryMapping, if the JVM was started with parameter-dsun.zip.disablememorymapping=true, The JVM then does not crash when it encounters this situation.

Of course, this property cannot be overly dependent, because the jar file being updated when it is load may cause the program to perform an exception and make it more prone to problems such as bugs.

Original: http://blog.csdn.net/hongchangfirst/article/details/78950369

Author: Hongchangfirst

Hongchangfirst's homepage: http://blog.csdn.net/hongchangfirst