hs_err_pid這種文件，是JVM出現(xiàn)錯誤時dump下來的。記錄了錯誤發(fā)生當(dāng)時：

1）JVM的狀態(tài)參數(shù)

2）Linux的狀態(tài)參數(shù)

?就以下面的文件為例：

# # There is insufficient memory for the Java Runtime Environment to continue. # Cannot create GC thread. Out of system resources. # Possible reasons: # The system is out of physical RAM or swap space # In 32 bit mode, the process size limit was hit # Possible solutions: # Reduce memory load on the system # Increase physical memory or swap space # Check if swap backing store is full # Use 64 bit Java on a 64 bit OS # Decrease Java heap size (-Xmx/-Xms) # Decrease number of Java threads # Decrease Java thread stack sizes (-Xss) # Set larger code cache with -XX:ReservedCodeCacheSize= # This output file may be truncated or incomplete. # # Out of Memory Error (gcTaskThread.cpp:48), pid=92270, tid=140070527960832 # # JRE version: (8.0_77-b03) (build ) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.77-b03 mixed mode linux-amd64 compressed oops) # Core dump written. Default location: /data/home/data_monitor/dmonitor/dmonitor/core or core.92270 (max size 100000 kB). To ensure a full core dump, try "ulimit -c unlimite d" before starting Java again #

?出現(xiàn)上述文件的可能原因是：

1）內(nèi)存不夠

2）進程打開數(shù)達到上限

?

1、釋放內(nèi)存
請參看這篇文章

?http://www.cnblogs.com/kangoroo/p/7375604.html

2、修改進程打開數(shù)上限

修改文件/etc/security/limits.conf

idata@qa-f1502-xg01.xg01:~$ vim /etc/security/limits.conf

修改例子如下

arch soft nproc 102400 arch hard nproc 102400

第一列：linux系統(tǒng)用戶名，*代表所有

第二列：軟連接/硬鏈接

第三列：類型，nproc-進程的數(shù)量/nofile-文件打開數(shù)/core-core文件大小

第四列：數(shù)量

?

轉(zhuǎn)載于:https://www.cnblogs.com/kangoroo/p/7409952.html

總結(jié)

以上是生活随笔為你收集整理的hs_err_pid的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔推薦給好友。