【问题标题】:Jenkins gives error "Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded"?Jenkins 给出错误“线程“主”java.lang.OutOfMemoryError 中的异常:超出 GC 开销限制”?
【发布时间】:2016-10-02 00:14:44
【问题描述】:

在 jenkins 中构建项目时,出现 OutofBoundMemory 错误。 日志是这样的。。

Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
    at org.sonar.sslr.internal.vm.Machine.createNode(Machine.java:256)
    at org.sonar.sslr.internal.vm.Instruction$RetInstruction.execute(Instruction.java:305)
    at org.sonar.sslr.internal.vm.Machine.execute(Machine.java:162)
    at org.sonar.sslr.internal.vm.Machine.execute(Machine.java:106)
    at org.sonar.sslr.internal.vm.Machine.parse(Machine.java:84)
    at org.sonar.sslr.parser.ParseRunner.parse(ParseRunner.java:45)
    at com.sonar.sslr.api.typed.ActionParser.parse(ActionParser.java:102)
    at com.sonar.sslr.api.typed.ActionParser.parse(ActionParser.java:91)
    at org.sonar.php.PHPAnalyzer.nextFile(PHPAnalyzer.java:71)
    at org.sonar.plugins.php.PHPSensor.analyseFile(PHPSensor.java:142)
    at org.sonar.plugins.php.PHPSensor.analyseFiles(PHPSensor.java:124)
    at org.sonar.plugins.php.PHPSensor.analyse(PHPSensor.java:115)
    at org.sonar.batch.phases.SensorsExecutor.executeSensor(SensorsExecutor.java:58)
    at org.sonar.batch.phases.SensorsExecutor.execute(SensorsExecutor.java:50)
    at org.sonar.batch.phases.AbstractPhaseExecutor.execute(AbstractPhaseExecutor.java:83)
    at org.sonar.batch.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:192)
    at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:142)
    at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:127)
    at org.sonar.batch.scan.ProjectScanContainer.scan(ProjectScanContainer.java:241)
    at org.sonar.batch.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:236)
    at org.sonar.batch.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:226)
    at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:142)
    at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:127)
    at org.sonar.batch.task.ScanTask.execute(ScanTask.java:47)
    at org.sonar.batch.task.TaskContainer.doAfterStart(TaskContainer.java:86)
    at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:142)
    at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:127)
    at org.sonar.batch.bootstrap.GlobalContainer.executeTask(GlobalContainer.java:106)
    at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:119)
    at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(BatchIsolatedLauncher.java:62)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

我猜即使构建持续了很长时间.. 我正在使用 sonarqube runner 我该怎么办?

【问题讨论】:

    标签: jenkins sonarqube sonarqube-scan


    【解决方案1】:

    在构建步骤的“JVM 选项”输入中,您需要为进程指定更多内存(比默认值)。这可能是这样的:

    -Xmx2g -Xms512m -XX:MaxPermSize=512m

    请注意,您应根据系统资源调整这些值。

    【讨论】:

    • WARN: [JOURNAL_FLUSHER] WARNING 日志刷新操作过去 8 个周期花费了 13,180 毫秒,平均为 1,647 毫秒我收到此警告。我已将值设置为 1024。你能告诉它是什么意思
    猜你喜欢
    • 2018-06-13
    • 2011-10-06
    • 1970-01-01
    • 2014-05-15
    • 2010-11-26
    • 1970-01-01
    • 1970-01-01
    • 2018-08-13
    相关资源
    最近更新 更多