声纳 findbugs 堆大小 [英] sonar findbugs heap size

问题描述

我是声纳新手.我正在使用声纳 pulgin 从 Jenkins 运行声纳.

i am new to sonar. i am running sonar from Jenkins with sonar pulgin.

当我从 jenkins 运行时，我在 findbugs 处出现内存不足异常

When i am running from jenkins i am getting out of memory exception at findbugs

以下是错误:

 Out of memory
Total memory: 1037M
 free memory: 30M
Analyzed: D:VictorautocreatedwebappWEB-INFclasses
     Aux: C:DOCUME~1NADBHA~1LOCALS~1Tempfindbugs4165854405681394173.jar
     Aux: C:DOCUME~1NADBHA~1LOCALS~1Tempfindbugs4688505485649811865.jar
Total time: 2:04:49.155s
Final Memory: 358M/989M
Exception in thread "main" org.sonar.batch.bootstrapper.BootstrapException: org.sonar.api.utils.SonarException: Can not execute Findbugs
    at org.sonar.runner.Runner.delegateExecution(Runner.java:189)
    at org.sonar.runner.Runner.execute(Runner.java:78)
    at org.sonar.runner.Main.main(Main.java:61)
Caused by: org.sonar.api.utils.SonarException: Can not execute Findbugs
    at org.sonar.plugins.findbugs.FindbugsExecutor.execute(FindbugsExecutor.java:120)
    at org.sonar.plugins.findbugs.FindbugsSensor.analyse(FindbugsSensor.java:58)
    at org.sonar.batch.phases.SensorsExecutor.execute(SensorsExecutor.java:64)
    at org.sonar.batch.phases.Phases.execute(Phases.java:93)
    at org.sonar.batch.bootstrap.ProjectModule.doStart(ProjectModule.java:143)
    at org.sonar.batch.bootstrap.Module.start(Module.java:83)
    at org.sonar.batch.bootstrap.BatchModule.analyze(BatchModule.java:111)
    at org.sonar.batch.bootstrap.BatchModule.doStart(BatchModule.java:101)
    at org.sonar.batch.bootstrap.Module.start(Module.java:83)
    at org.sonar.batch.bootstrap.BootstrapModule.doStart(BootstrapModule.java:102)
    at org.sonar.batch.bootstrap.Module.start(Module.java:83)
    at org.sonar.batch.Batch.execute(Batch.java:100)
    at org.sonar.runner.Launcher.executeBatch(Launcher.java:65)
    at org.sonar.runner.Launcher.execute(Launcher.java:58)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.sonar.runner.Runner.delegateExecution(Runner.java:186)
    ... 2 more
Caused by: java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space
    at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
    at java.util.concurrent.FutureTask.get(Unknown Source)
    at org.sonar.plugins.findbugs.FindbugsExecutor.execute(FindbugsExecutor.java:112)
    ... 20 more
Caused by: java.lang.OutOfMemoryError: Java heap space

我的声纳版本是 2.13

my sonar version is 2.13

当我将 Jenkins 声纳插件中的 jvm 选项增加到 1280 时，会显示以下错误:

when i am increasing the jvm options in Jenkins sonar plugin to 1280 it is shown below error:

Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit`enter code here`

推荐答案

是的，如果分析的代码库很大，sonar findbugs executor 可以使用大量 RAM.

Yes, the sonar findbugs executor can use a lot of RAM if the analyzed code base is large.

您不仅要增加 JVM 可用的堆大小，还要增加MaxPermSize"和ReservedCodeCacheSize"(至少对于 Java Hotspot VM).必须在实际执行 FindBugs 声纳执行器的 JVM 上设置 JVM 选项.所以可能不是 Jenkins 虚拟机，而是 Jenkins 为这项工作启动的虚拟机.

You will have to increase not only the heap size available to the JVM, but also "MaxPermSize" and "ReservedCodeCacheSize" (at least for the Java Hotspot VM). The JVM options must be set on the JVM which is actually executing the FindBugs sonar executor. So probably not the Jenkins VM, but the one that Jenkins starts for the job.

以下是 64 位系统的示例:

Here's an example for a 64bit system:

-Xmx3062m -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=128m

在我假设您正在使用的 32 位系统上，您会选择较低的值，例如:

On a 32bit system, which I am assuming you are using, you would go for lower values, such as:

-Xmx1536m -XX:MaxPermSize=384m -XX:ReservedCodeCacheSize=128m

另外，如果 Jenkins 不接受 JVM 选项，您可以尝试使用 Jenkins 的 sonar ant 任务运行声纳.(这就是我正在做的，我可以设置尽可能多的内存.)

Also, if Jenkins won't accept the JVM options, you can try running sonar using the sonar ant task from Jenkins. (That's what I am doing, and I can set as much memory as I like.)

这篇关于声纳 findbugs 堆大小的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！