SonarLint error during analysis with latest intellij and remote SonarQube server

the SonarLint plugin on IntelliJ doesn’t work anymore when binding to a SonarQube server

versions used :

  • SonarLint
  • IntelliJ ultimate 2019.2.1 Ultimate
  • SonarQube server 6.7.4

error observed :

Files analysis fails with message : "Using configuration of ‘xxx’ in server ‘yyy’
Analysing ‘’…
File won’t be refreshed because there were errors during analysis
(xxx and yyy are correctly set)

The exact same configuration works fine with IntelliJ 2019.1.3

Maybe it is related to the kind of old version of SonarQube we have, let me know if you think so

Thanks for the support


I’m having exactly the same issue here using the same versions of SonarLint and IntelliJ but SonarQube server 7.0 (build 36138).
Unfortunately I’ve updated to IntelliJ 2019.2 and additionally installed JDK 11 in parallel so maybe this error is related to the Java version? The SonarQube server supports JDK 8 only so far.
Best regards


the same here, using:
IDEA 2019.2.2
Ubuntu 16.04
… and connecting to SQ 7.2.1

Since my colleagues meanwhile get the same error we decided to estimate this issue a bit deeper.
SonarLint plugin version is now
Running with the configuration from my post above we found this in the log:

Starting analysis with configuration:
extraProperties: {,
Configured Java source version ( 8
Unable to create symbol table for : …/
java.lang.IllegalArgumentException: Unsupported class file major version 55
at org.objectweb.asm.ClassReader.(
at org.objectweb.asm.ClassReader.(
at org.objectweb.asm.ClassReader.(
at org.sonarsource.sonarlint.core.analyzer.sensor.SensorsExecutor.executeSensor(
at org.sonarsource.sonarlint.core.analyzer.sensor.SensorsExecutor.execute(
at org.sonarsource.sonarlint.core.container.analysis.AnalysisContainer.doAfterStart(
at org.sonarsource.sonarlint.core.container.ComponentContainer.startComponents(
at org.sonarsource.sonarlint.core.container.ComponentContainer.execute(
at org.sonarsource.sonarlint.core.ConnectedSonarLintEngineImpl.lambda$analyze$0(
at org.sonarsource.sonarlint.core.ConnectedSonarLintEngineImpl.withReadLock(
at org.sonarsource.sonarlint.core.ConnectedSonarLintEngineImpl.withReadLock(
at org.sonarsource.sonarlint.core.ConnectedSonarLintEngineImpl.analyze(
at org.sonarlint.intellij.core.ConnectedSonarLintFacade.analyze(
at org.sonarlint.intellij.core.SonarLintFacade.startAnalysis(
at org.sonarlint.intellij.analysis.SonarLintAnalyzer.analyzeModule(
at org.sonarlint.intellij.analysis.SonarLintTask.analyze(
at org.sonarlint.intellij.analysis.SonarLintJobManager.lambda$runTask$1(
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(
at org.sonarlint.intellij.analysis.SonarLintJobManager.lambda$runTask$2(
at java.base/java.util.concurrent.Executors$
at java.base/
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.base/java.util.concurrent.ThreadPoolExecutor$
at java.base/

So it looks like SonarLint tries to analyse a class compiled with JDK 11 but expects a JDK 8 compiled class. Any ideas??

1 Like

Hi @florian, thanks for investigating this deeper on your side.

As far as I can tell, “official” support for Java 11-compatible class files (major version 55) was brought with SonarJava 5.8, released in October 2018, the critical component here being ASM 6.2.1.

I understand that you are using connected mode with SonarQube 7.0, could you please check which version of SonarJava is installed?

Another thing you could check is that your project in IntelliJ is properly configured to compile Java 8-compatible class files (major version 52).

Hi @JBL_SonarSource,

thanks for your feedback,
My project in IntelliJ is still configured to use Java8 but for other projects I’ve also installed JDK 11.
The SonarQube server 7.0 (build 36138) is running with SonarJava 5.6 (build 15032).

Probably an update of the SonarJava plugin would fix my problems but this also requires an update of the SonarQube server which I cannot do in the short run.

I was hoping there is another way to make this work since everything is fine on the SonarQube server and only the SonarLint plugin refuses to do anything.

Hi all,
I got the same exception as Florian posted before on a Maven project:

  • 1.8
  • maven.compiler.source: 1.8
  • 1.8

java.lang.IllegalArgumentException: Unsupported class file major version 55

To make sure, that the code is compiled for Java 8 I inspected the Maven target directory:

$ javap -verbose MyClass.class | grep "major"
major version: 52


  • JDK: 8.0.222
  • IDE
    • Build version: IntelliJ IDEA 2019.2.2 Build #IU-192.6603.28 September 6, 2019
    • Java version: 11.0.3+12-b304.56x86_64
    • Operating System: Mac OS X (10.14.6, x86_64)
    • JVM version: OpenJDK 64-Bit Server VM JetBrains s.r.o
  • SonarLint (

Now I changed the IntelliJ IDEA’s Java runtime to JDK 8 (

  • Build version: IntelliJ IDEA 2019.2.2 Build #IU-192.6603.28 September 6, 2019
  • Java version: 1.8.0_161-b12x86_64
  • Operating System: Mac OS X (10.14.6, x86_64)
  • JVM version: Java HotSpot™ 64-Bit Server VM Oracle Corporation

Result: Sonarlint works as expected. No exception.

It looks like the Sonarlint plugin uses JDK from IntelliJ instead of choosing the JDK according to the project settings (


I think I understand what is going on.

TL;DR: the best fix to this issue is to update SonarJava on the server to a version greater than 5.8, and the second best fix is indeed to run IntelliJ with a JDK 8.

My hypothesis is that SonarLint, as an IntelliJ extension, runs inside IntelliJ’s VM. So it also loads the SonarJava analyzer inside this same VM, no matter what is configured at the project level. SonarJava in turn tries to load classes from IntelliJ’s VM when resolving classes used by MyClass - e.g, java.lang.Object - and gets the aforementioned ASM error.

As far as I can tell, there is no way to tell SonarJava to load Java standard library classes from another version than the one it is running with, hence my advice to upgrade SonarJava to a version that supports Java 11.

sounds reasonable

As the first version with Java 11 support (SQ 7.3) has been released over a year ago I guess it’s time for an upgrade :wink:

Thanks for your assistance.

You can select IntelliJ runtime :

Beware that last plugin version is built with JDK 11 so if you choose an older JDK it won’t work anymore and you will have to install a previous version (been there…).