GC开销限制超出了5.5版中正在运行的后台任务 [英] GC overhead limit exceeded running background task in version 5.5

问题描述

我正在使用以下包装器配置设置运行SonarQube 5.5.

I am running SonarQube 5.5 with the following wrapper config settings.

wrapper.java.initmemory=3
wrapper.java.maxmemory=4096

我仍在获取以下堆栈跟踪信息，该项目已在sonarqube 5.3中成功运行.

I am still getting the following stack trace, this project has run successfully with sonarqube 5.3.

2016.05.09 11:14:09 INFO  [o.s.s.c.s.ComputationStepExecutor] Compute coverage measures | time=105ms
2016.05.09 11:14:09 INFO  [o.s.s.c.s.ComputationStepExecutor] Compute comment measures | time=120ms
2016.05.09 11:14:14 INFO  [o.s.s.c.s.ComputationStepExecutor] Copy custom measures | time=5667ms
2016.05.09 11:14:15 INFO  [o.s.s.c.s.ComputationStepExecutor] Compute duplication measures | time=424ms
2016.05.09 11:14:26 ERROR [o.s.s.c.c.ComputeEngineContainerImpl] Cleanup of container failed
java.lang.OutOfMemoryError: GC overhead limit exceeded
2016.05.09 11:14:26 ERROR [o.s.s.c.t.CeWorkerCallableImpl] Failed to execute task AVSWNiXkOySW07vtMalp
java.lang.OutOfMemoryError: GC overhead limit exceeded
    at java.util.Arrays.copyOfRange(Arrays.java:3664) ~[na:1.8.0_45]
    at java.lang.StringBuffer.toString(StringBuffer.java:671) ~[na:1.8.0_45]
    at java.io.StringWriter.toString(StringWriter.java:210) ~[na:1.8.0_45]
    at org.apache.commons.lang.Entities.escape(Entities.java:838) ~[commons-lang-2.6.jar:2.6]
    at org.apache.commons.lang.StringEscapeUtils.escapeXml(StringEscapeUtils.java:620) ~[commons-lang-2.6.jar:2.6]
    at org.sonar.server.computation.step.DuplicationDataMeasuresStep$DuplicationVisitor.appendDuplication(DuplicationDataMeasuresStep.java:129) ~[sonar-server-5.5.jar:na]

推荐答案

必须在sonar.properties中进行内存调整:

Memory adjustments must be made in sonar.properties:

• sonar.web.javaOpts(对于Web Server JVM)
• sonar.ce.javaOpts(对于Compute Engine JVM)
• sonar.search.javaOpts(对于运行ElasticSearch的JVM).

• sonar.web.javaOpts (for Web Server JVM)
• sonar.ce.javaOpts (for Compute Engine JVM)
• sonar.search.javaOpts (for JVM running ElasticSearch).

在您的情况下，内存异常发生在后台任务中，因此它与Compute Engine有关(请参见

In your case the memory exception occurs in a background task so it relates to Compute Engine (see SonarQube architecture for more insight).

wrapper.conf中的设置与此处无关，应保持不变(因此文件中的# DO NOT EDIT THE FOLLOWING SECTIONS警告).

Settings in wrapper.conf are not relevant here and should be left untouched (hence the # DO NOT EDIT THE FOLLOWING SECTIONS warning in the file).

这篇关于GC开销限制超出了5.5版中正在运行的后台任务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！