JVM在java.util.zip.ZipFile.getEntry中崩溃_java

概述JVM在java.util.zip.ZipFile.getEntry中崩溃

以下日志文件导致JVM崩溃。

# # A Fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f60ddce2058,pID=117268,tID=140052313204480 # # JRE version: Java(TM) SE Runtime Environment (7.0_51-b13) (build 1.7.0_51-b13) # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.51-b03 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libzip.so+0x5058] ZIP_GetEntry+0x78 # # Failed to write core dump. Core dumps have been Disabled. To enable core dumPing,try "ulimit -c unlimited" before starting Java again # # If you would like to submit a BUG report,please visit: # http://BUGreport.sun.com/BUGreport/crash.Jsp # The crash happened outsIDe the Java Virtual Machine in native code. # See problematic frame for where to report the BUG. # --------------- THREAD --------------- Current thread (0x00007f5f4c01a800): JavaThread "EJB default - 3" [_thread_in_native,ID=117526,stack(0x00007f607850e000,0x00007f607860f000)] siginfo:si_signo=SIGSEGV: si_errno=0,si_code=1 (SEGV_MAPERR),si_addr=0x0000000000000278 Registers: RAX=0x0000000000000000,RBX=0x00007f607860c3c0,RCX=0x0000003a4d2182a0,RDX=0x000000000000009e RSP=0x00007f607860c370,RBP=0x00007f607860c3a0,RSI=0x00007f5fdc0060a1,RDI=0x0000000000000010 R8 =0x00000000000001e5,R9 =0x2e786176616a2f73,R10=0x6e6172742e6c6d78,R11=0x0000000741902898 R12=0x00007f5fdc006340,R13=0x00007f5f4c01a9e8,R14=0x0000000066c00f1d,R15=0x00007f607860c3c0 RIP=0x00007f60ddce2058,EFLAGS=0x0000000000010246,CSGSFS=0x0000000000000033,ERR=0x0000000000000004 TRAPNO=0x000000000000000e top of Stack: (sp=0x00007f607860c370) 0x00007f607860c370: 000000387860c3a0 00007f607860c3c0 0x00007f607860c380: 0000000000000038 00007f5f4c01a9e8 0x00007f607860c390: 00007f607860c3c0 00007f607860c818 0x00007f607860c3a0: 00007f607860c800 00007f60ddce0eed 0x00007f607860c3b0: 01007f5f4c01b6d0 00007f5fdc006340 0x00007f607860c3c0: 464e492d4154454d 656369767265732f 0x00007f607860c3d0: 2e786176616a2f73 6e6172742e6c6d78 0x00007f607860c3e0: 72542e6d726f6673 656d726f66736e61 0x00007f607860c3f0: 79726f7463614672 00007f6078600000 0x00007f607860c400: 00007f5f4c01a9e8 0000000000000000 0x00007f607860c410: 00007f607860cc90 00007f60d5006233 0x00007f607860c420: 00007f60d5005310 00007f6000000000 0x00007f607860c430: 00007f607860cce0 00007f607860cc90 0x00007f607860c440: 00007f5f4c01a800 00007f5f4c00d970 0x00007f607860c450: 00007f5f4c01b690 00007f5f4c01b6e0 0x00007f607860c460: 00007f5f4c01ba78 00000000000003d8 0x00007f607860c470: 00007f607860da90 00000005402d81a0 0x00007f607860c480: 00007f60d256f5c0 00007f5f4c01b6d8 0x00007f607860c490: 00007f607860cc90 00007f5f4c01a800 0x00007f607860c4a0: 00007f5f4c01b6d0 00007f5f4c01b6d8 0x00007f607860c4b0: 00007f607860cc90 00007f5f4c01a800 0x00007f607860c4c0: 00007f5fa8003ac0 00007f5fa8003ac0 0x00007f607860c4d0: 00007f607860cd20 00007f60decc9d8d 0x00007f607860c4e0: 00007f607860c500 00007f607860cd30 0x00007f607860c4f0: 00007f5f4c01a9e8 0000000000000000 0x00007f607860c500: 00007f607860cd80 00007f60d5006233 0x00007f607860c510: 00007f60d5005310 00007f6000000000 0x00007f607860c520: 00007f607860cdd8 00007f607860cd80 0x00007f607860c530: 00007f5f4c01a800 00007f5f4c01a800 0x00007f607860c540: 00007f5fa8003ac0 00007f5fa8003ac0 0x00007f607860c550: 00007f5f4c01b6c8 00007f60decc9d8d 0x00007f607860c560: 00007f607860c580 0000000000000410 Instructions: (pc=0x00007f60ddce2058) 0x00007f60ddce2038: 45 85 c0 0f 84 ff 00 00 00 44 89 f0 31 d2 41 f7 0x00007f60ddce2048: b4 24 88 00 00 00 49 8b 84 24 80 00 00 00 89 d2 0x00007f60ddce2058: 8b 1c 90 0f 1f 44 00 00 4d 8b ac 24 98 00 00 00 0x00007f60ddce2068: 4d 85 ed 74 1e 49 8b 7d 00 4c 89 fe e8 cf d7 ff Register to memory mapPing: RAX=0x0000000000000000 is an unkNown value RBX=0x00007f607860c3c0 is pointing into the stack for thread: 0x00007f5f4c01a800 RCX=0x0000003a4d2182a0: <offset 0x2182a0> in /lib64/libpthread.so.0 at 0x0000003a4d000000 RDX=0x000000000000009e is an unkNown value RSP=0x00007f607860c370 is pointing into the stack for thread: 0x00007f5f4c01a800 RBP=0x00007f607860c3a0 is pointing into the stack for thread: 0x00007f5f4c01a800 RSI=0x00007f5fdc0060a1 is an unkNown value RDI=0x0000000000000010 is an unkNown value R8 =0x00000000000001e5 is an unkNown value R9 =0x2e786176616a2f73 is an unkNown value R10=0x6e6172742e6c6d78 is an unkNown value R11=0x0000000741902898 is an unkNown value R12=0x00007f5fdc006340 is an unkNown value R13=0x00007f5f4c01a9e8 is an unkNown value R14=0x0000000066c00f1d is an unkNown value R15=0x00007f607860c3c0 is pointing into the stack for thread: 0x00007f5f4c01a800 Stack: [0x00007f607850e000,0x00007f607860f000],sp=0x00007f607860c370,free space=1016k Native frames: (J=compiled Java code,j=interpreted,Vv=VM code,C=native code) C [libzip.so+0x5058] ZIP_GetEntry+0x78 C [libzip.so+0x3eed] Java_java_util_zip_Zipfile_getEntry+0xad J java.util.zip.Zipfile.getEntry(J[BZ)J Java frames: (J=compiled Java code,Vv=VM code) J java.util.zip.Zipfile.getEntry(J[BZ)J J java.util.jar.Jarfile.getEntry(Ljava/lang/String;)Ljava/util/zip/ZipEntry; J org.jboss.modules.JarfileResourceLoader.getResource(Ljava/lang/String;)Lorg/jboss/modules/Resource; J org.jboss.modules.ModuleClassLoader.loadResourceLocal(Ljava/lang/String;)Ljava/util/List; J org.jboss.modules.Module.getResourceAsstream(Ljava/lang/String;)Ljava/io/inputStream;

在第一次发生这种情况时，我提到了一些在线资料，我把JVM选项-Dsun.zip.disableMemoryMapPing=true 。但是同样的JVM崩溃正在发生。在不同的地方有许多相似的报道问题，但没有一个答案为这个问题提供了坚实的解决scheme。

我已经通过了以下post。但是我没有办法解决。

在类加载期间，memcpy会导致JVM崩溃

使用Powershell或命令行在windows中创build压缩/压缩文件夹

Python 压缩模块在linux上是线程安全的吗？在Google App Engine上？

gzip – 关于性能的问题

如何使用dotnet框架4.0提取zip文件，而无需使用第三方dll

Nginx的服务器内容gzip compress不能正常工作

任何帮助，高度赞赏。

如何用tar压缩目录时排除大文件

如何使用Java创build一个非常具体的zip文件结构

在postrotate脚本之后，logrotate压缩文件