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