1. 程式人生 > >There is insufficient memory for the Java Runtime Environment to continue. 解決

There is insufficient memory for the Java Runtime Environment to continue. 解決

在Centos  6.4 X64, JDK 1.7 U21下用hadoop 1.2.1 執行 mahout 0.9,處理一個5GB的資料,系統提示There is insufficient memory for the Java Runtime Environment to continue.

14/07/15 08:46:05 INFO mapred.JobClient: Task Id : attempt_201407141818_0002_m_000018_0, Status : FAILED
java.lang.Throwable: Child Error
        at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:271)
Caused by: java.io.IOException: Task process exit with nonzero status of 1.
        at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)


attempt_201407141818_0002_m_000018_0: #
attempt_201407141818_0002_m_000018_0: # There is insufficient memory for the Java Runtime Environment to continue.


attempt_201407141818_0002_m_000018_0: # Cannot create GC thread. Out of system resources.
attempt_201407141818_0002_m_000018_0: # An error report file with more information is saved as:
attempt_201407141818_0002_m_000018_0: # /home/hadoop/hd_space/mapred/local/taskTracker/hadoop/jobcache/job_201407141818_0002/attempt_201407141818_0002_m_000018_0/work/hs_err_pid25377.log
14/07/15 08:46:07 INFO mapred.JobClient:  map 15% reduce 0%
14/07/15 08:46:09 INFO mapred.JobClient:  map 16% reduce 0%
14/07/15 08:46:09 INFO mapred.JobClient: Task Id : attempt_201407141818_0002_m_000018_1, Status : FAILED
java.lang.Throwable: Child Error
        at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:271)
Caused by: java.io.IOException: Task process exit with nonzero status of 1.
        at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)


attempt_201407141818_0002_m_000018_1: #
attempt_201407141818_0002_m_000018_1: # There is insufficient memory for the Java Runtime Environment to continue.
attempt_201407141818_0002_m_000018_1: # Cannot create GC thread. Out of system resources.
attempt_201407141818_0002_m_000018_1: # An error report file with more information is saved as:

檢視系統限制

[[email protected] ~]# ulimit -a
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 2066288
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files  

                   (-n) 1024
pipe size            (512 bytes, -p) 8

檔案數太少了。檢視系統的/etc/security/limit.conf,etc/sysctl.conf ,換JDK版本等等,均無果!

在Root下設定 ulimit -c unlimited後,仍然不行。

[[email protected] mahout-distribution-0.9]$  ulimit -a

max user processes              (-u) 1024
virtual memory          (kbytes, -v) unlimited

經過查證,再在/etc/security/下一看。centos6多出來一個limits.d目錄,下面有個檔案: 90-nproc.config
此檔案內容:
# Default limit for number of user's processes to prevent
# accidental fork bombs.
# See rhbz #432903 for reasoning.


*          soft    nproc     1024
root       soft    nproc     unlimited
這裡限制了1024呀,果斷註釋。

問題解決。

相關推薦

There is insufficient memory for the Java Runtime Environment to continue. 解決

在Centos  6.4 X64, JDK 1.7 U21下用hadoop 1.2.1 執行 mahout 0.9,處理一個5GB的資料,系統提示There is insufficient memory for the Java Runtime Environment to

eplise中運行提示 A fatal error has been detected by the java runtime environment

mage image 截圖 src fatal env 分享圖片 detect 版本 今天一同事出現運行項目時,提示 A fatal error has been detected by the java runtime environment,具體表現是使用我們框架,不能

解決:A fatal error has been detected by the Java Runtime Environment

Tomcat 崩潰日誌: # # A fatal error has been detected by the Java Runtime Environment: # #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x1db7ae66

tomcat執行時異常“A fatal error has been detected by the Java Runtime Environment:”

背景   tomcat跑好好的,突然崩了。上線看log發現提示如下異常。 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f

A fatal error has been detected by the Java Runtime Environment程式錯誤處理方法

# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x70e72b89, pid=8

Tomcat啟動:A fatal error has been detected by the Java Runtime Environment

解決辦法:讓jvm跳過該方法的編譯  1.如果是MyEclipse下啟動服務,則在Window-preference-java-installed jres 裡面設定, 在 defalt vm arguments 填入下邊的程式碼就可以了!  程式碼:          

Tomcat啟動:A fatal error has been detected by the Java Runtime Environment(JVM Crash分析及相關資料)

2013年1月10號注: 今天更新程式碼之後,突然出現一個問題:Tomcat啟動時,總是會出現jvm fatal error錯誤導致tomcat無法正常啟動,以下是錯誤資訊: # # A f

mybatis 異常 There is no getter for property named 'bizId' in 'class java.lang.Long'

img 技術分享 .com mybatis lan alt nbsp pro 錯誤 mybatis 異常 There is no getter for property named ‘bizId‘ in ‘class java.lang.Long‘ 當使用mybatis進行

There is insufficient system memory to run this query 錯誤

版本 system sql nim 分享 想想 ros creat board 服務器環境大致情況如下: 操作系統: Microsoft Windows Server 2003 R2 Enterprise Edition Service Pack 2 數據庫 :

There is no getter for property named xxx' in 'class java.lang.xxx'

public med 入參 ren 說明 _id lang list val 在xxxMapper.xml我們使用sql片段來提高sql代碼的復用性,當時新手傳入參數時常常出現這樣的錯誤: There is no getter for property na

Mybatis 報錯 There is no getter for property named '***' in 'class java.lang.String'

sql 使用 mybatis and 參數 when choose orcal get 在mapper.xml中 , 如果單參數是String類型 , 且在sql語句中對參數進行了判斷 , 如下 when 中的判斷 , 如果出現 if 判斷也是一樣的。都需要把判斷中的參

There is no getter for property named 'xxx' in 'class java.lang.String

code app select unknown cep proxy sun myba bat 報錯信息: org.mybatis.spring.MyBatisSystemException: nested exception is org.apache.ibatis.

freemind 運行就報錯~"The registry refers to a nonexistent Java Runtime Environment installation or the runtime is corrupted."

隨著 進行 freemind refers es2017 無法 希望 ges 生成 最近在安裝使用freemind的時候,安裝下來無法使用,打開後立馬報錯~ 錯誤原因: 更新jdk以後,註冊表裏面沒有隨著更新jdk的版本和位置; 絕對可行的方法: 1. 進入控制面板--程

Mybatis異常There is no getter for property named 'XXX' in 'class java.lang.String'

for ava 異常 public rom title mpc mybatis string Mybatis版本:mybatis-3.0.6.jar 1.當入參為 string類型時 (包括java.lang.String.) 我們使用#{xxx}引入參數.會拋異

mybatis之org.apache.ibatis.reflection.ReflectionException: There is no getter for property named 'time' in 'class java.lang.String'

mybatis 圖片 配置 style pac prop bubuko type PE mybatis接口 List<String> getUsedCate(String time); 配置文件 <select id="getUsed

Mybatis中傳參包There is no getter for property named 'XXX' in 'class java.lang.String'

col mybatis hone mybatis查詢 默認 lec named ongl bsp Mybatis中傳參包There is no getter for property named ‘XXX‘ in ‘class java.lang.String‘ 一、發現

mybaits錯誤解決There is no getter for property named 'id' in class 'java.lang.String'

在使用mybaitis傳引數的時候,如果僅傳入一個型別為String的引數,那麼在 xml檔案中應該使用_parameter來代替引數名。 正確的寫法: <span style="font-size:18px;"> <!-- 用於查詢運單

Mybatis異常There is no getter for property named 'XXX' in 'class java.lang.String'

1.當入參為 string型別時 (包括java.lang.String.) 我們使用#{xxx}引入引數.會拋異常There is no getter for property named ‘XXX’ in ‘class java.lang.String’

解決mybatis報錯 There is no getter for property named ... in 'class java.lang.String'

發生這個的原因就是對於的屬性欄位沒有書寫正確,導致報錯。 這型別的報錯類似There is no getter for property named ... in 'classXXX。一個主要原因是在xml中進行引數配置的時候,引數名稱書寫錯誤。這個也是我遇到的問題。 為

There is no getter for property named 'title' in 'class java.lang.String'

錯誤原因如下 <select id="getSoftToolList" parameterType="String" resultType="SoftTool">