Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8145260

To bring j.u.z.ZipFile's native implementation to Java to remove the expensive jni cost and mmap crash risk [2]


    • Type: Enhancement
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 8, 9
    • Fix Version/s: 9
    • Component/s: core-libs
    • Labels:



        The current j.u.z.ZipFile has following major issues:

        (1) Its ZIP file format support code is in native C code (shared with the VM via ZipFile.c -> zip_util.c). Any entry lookup, creation requires multiple round-trip of expensive jni invocations.

        (2) The current native C implementation code uses mmap to map in the central directory table appears to be a big risk of vm crash when the underlying jar file gets overwritten with new contents while it is still being used by other ZipFile.

        (3) The use of "filename + lastModified()" cache (at native) appears to be broken if the timestamp is in low resolution,and/or the file is being overwritten.

        The clean solution here is to bring the ZIP format support code from native to Java to remove the jni invocation cost and the mmap risk. Also to use the fileKey and lastModified from java.nio.file.attribute.BasicFileAttributes to have better cache matching key.


        The first try of this enhancement JDK-8142508 failed (which causes jtreg fails in -avm mode for those testng tests). This issue is used to integrate the updated change for JDK-8142508


            Issue Links



                • Assignee:
                  sherman Xueming Shen
                  sherman Xueming Shen
                • Votes:
                  0 Vote for this issue
                  8 Start watching this issue


                  • Created: