Random JVM crashes during the sonar analysis

[Marco Cicolini]

Hey,

We have a sonar setup with roughly 200 projects (version 5.1.2), where we have random JVM crashes during the analysis and we have a hard time to figure out what the real problem is.

The log output shows the following [1], I am not 100% sure about the interpretation of the output.

I guess the problem is during the execution of the BuildBreaker plugin and not of the sonar analysis itself.

Could someone please config this if I am right?

cheers,

marco

[1]: The log file:

[exec] 02:01:06.101 INFO - Analysis reports generated in 4473ms, dir size=24 KB
[exec] 02:01:09.915 INFO - Analysis reports compressed in 3813ms, zip size=63 KB
[exec] 02:01:09.954 INFO - Analysis reports sent to server in 39ms
[exec] 02:01:09.954 INFO - ANALYSIS SUCCESSFUL, you can browse ************************************************33
[exec] 02:01:09.955 INFO - Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report.
[exec] 02:01:09.956 INFO - Executing post-job class org.sonar.plugins.buildbreaker.AlertBreaker
[exec] 02:01:09.957 INFO - Executing post-job class org.sonar.plugins.buildbreaker.ForbiddenConfigurationBreaker
[exec] INFO: ------------------------------------------------------------------------
[exec] INFO: EXECUTION SUCCESS
[exec] INFO: ------------------------------------------------------------------------
[exec] Total time: 1:38.163s
[exec] Final Memory: 26M/908M
[exec] INFO: ------------------------------------------------------------------------
[exec] #
[exec] # A fatal error has been detected by the Java Runtime Environment:
[exec] #
[exec] # SIGSEGV (0xb) at pc=0x00007f4515197970, pid=21964, tid=139934958466816
[exec] #
[exec] # JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27)
[exec] # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops)
[exec] # Problematic frame:
[exec] # C 0x00007f4515197970
[exec] #
[exec] # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

[G. Ann Campbell]

I see this occasionally too on Cloudbees. It's apparently a bug in the JVM. When I see this, I upgrade the job's JVM and it goes away.

BTW, analysis has completed successfully (as shown in your log). I think the bug is hit when the JVM is shutting down.

Ann

[Marco Cicolini]

Thanks for the explanation, I will let the projects know so that they will upgrade the used java versions (some are still stuck with java 1.7 though).

cheers

marco

[Vijay Bandari]

Ann,

What java version you upgraded to? (We are on 1.8.0_66)

We recently (1 month) upgraded our sonar to 5.6.4 & yesterday our server is crashed with similar error.

I am trying to understand whether server side java version is causing this or scanner side java version.

Thanks,

Vijay Bandari

[G. Ann Campbell]

Hi Vijay,

Sorry, but it's been a long time since I looked at this and I no longer have access to the precise version string. I can only tell you it was a version of Java 8.

Ann