<< Back to previous view

[QB-3275] Need more details on Java OutofMemoryError on log
Created: 08/Oct/18  Updated: 19/Jan/19

Status: Closed
Project: QuickBuild
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Blocker
Reporter: Loïc Philippot Assigned To: Robin Shen
Resolution: Cannot Reproduce Votes: 0
Remaining Estimate: Unknown Time Spent: Unknown
Original Estimate: Unknown


 Description   
Hello,
In the log for java.lang.OutofMemoryError, it would be very usefull to have details as :
- Which build, agent and step are affected ?

Example of error :

2018-10-04 21:44:35,361 [pool-1-thread-6255] ERROR com.pmease.quickbuild.DefaultBuildEngine - Error processing build request.
  java.lang.RuntimeException: Error executing check condition job.
     at com.pmease.quickbuild.CheckConditionTask.reduce(CheckConditionTask.java:39)
     at com.pmease.quickbuild.CheckConditionTask.reduce(CheckConditionTask.java:16)
     at com.pmease.quickbuild.grid.GridTaskFuture.get(GridTaskFuture.java:155)
     at com.pmease.quickbuild.DefaultBuildEngine.process(DefaultBuildEngine.java:395)
     at com.pmease.quickbuild.DefaultBuildEngine.access$000(DefaultBuildEngine.java:143)
     at com.pmease.quickbuild.DefaultBuildEngine$2.run(DefaultBuildEngine.java:1233)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
    Caused by: java.lang.OutOfMemoryError: Java heap space

 Comments   
Comment by Robin Shen [ 09/Oct/18 12:01 AM ]
It is the build agent running the master step of the build. Please check agent log of it to see more details. Build agent memory can be increased by editing property "wrapper.java.maxmemory" in file "<build agent>/conf/wrapper.conf".
Generated at Thu Apr 25 16:04:43 UTC 2024 using JIRA 189.