JVM报错：Failed to write core dump. Core dumps have been disabled.

• 2019 年 10 月 7 日
• 笔记

版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文链接：https://blog.csdn.net/chengyuqiang/article/details/101192730

#  # A fatal error has been detected by the Java Runtime Environment:  #  #  SIGBUS (0x7) at pc=0x00007f9d3d100c50, pid=29904, tid=0x00007f9ca2bfb700  #  # JRE version: Java(TM) SE Runtime Environment (8.0_192-b12) (build 1.8.0_192-b12)  # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.192-b12 mixed mode linux-amd64 compressed oops)  # Problematic frame:  # C  [libzip.so+0x11c50]  newEntry.isra.4+0x60  #  # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again  #  # An error report file with more information is saved as:  # /opt/apache-tomcat-8.5.35/hs_err_pid29904.log  Compiled method (nm) 107233860  175     n 0       java.util.zip.ZipFile::getEntry (native)   total in heap  [0x00007f9d2916e050,0x00007f9d2916e3c0] = 880   relocation     [0x00007f9d2916e178,0x00007f9d2916e1c0] = 72   main code      [0x00007f9d2916e1c0,0x00007f9d2916e3c0] = 512  #  # If you would like to submit a bug report, please visit:  #   http://bugreport.java.com/bugreport/crash.jsp  # The crash happened outside the Java Virtual Machine in native code.  # See problematic frame for where to report the bug.

网上提供的解决办法，尝试如下

[root@elastic1 logs]# ulimit -c unlimited  [root@elastic1 logs]# ulimit -c -l  core file size          (blocks, -c) unlimited  max locked memory       (kbytes, -l) 64  [root@elastic1 logs]# 

这里备注一下：该方法并未解决问题，希望这里不要对其他网友产生误解。

下面一篇博文提供了解决思路 https://www.cnblogs.com/songyuejie/p/11221381.html

默认情况下Linux服务起的core core file size设置为0，需要调整该参数，但是这个参数并不能 解决问题； 问题的根本原因在于服务器的运行应用程序的打开文件的最大数及最大进程数设置的相对较小默认为4096 需要修改如下配置： /etc/security/limits.conf