SonarLint: frequent exceptions in console on Java test files

SonarQube for IDE Eclipse
1
  • Operating system: Windows 10
  • IDE name and version: Eclipse IDE for Java EE 2026-03 (4.39.0)
  • SonarQube for Eclipse plugin version: 12.1.0.84656
  • Programming language you’re coding in: Java, JS, TS
  • Is connected mode used: yes, SonarQube Cloud

And a thorough description of the problem / question:

SonarLint console has frequent exceptions

DBD analysis error: Dataflow bug detection analysis was interrupted because of an unexpected error.
java.lang.IllegalStateException: SonarLint cache doesn't contain IR file.
	at com.sonarsource.A.A.A.C.A(na:937)
	at com.sonarsource.A.A.A.B.C.<init>(na:1932)
	at com.sonarsource.A.A.A.B.D.A(na:3476)
	at com.sonarsource.A.A.A.F.I.C(na:1983)
	at com.sonarsource.A.E.C(na:2667)
	at com.sonarsource.A.A.A.F.I.A(na:44)
	at com.sonarsource.A.D.doExecute(na:268)
	at com.sonarsource.A.A.A.F.O.execute(na:2025)
	at org.sonarsource.sonarlint.core.analysis.container.analysis.sensor.SensorsExecutor.lambda$executeSensor$1(SensorsExecutor.java:102)
	at org.sonarsource.sonarlint.core.commons.tracing.Trace.startChild(Trace.java:63)
	at org.sonarsource.sonarlint.core.analysis.container.analysis.sensor.SensorsExecutor.executeSensor(SensorsExecutor.java:102)
	at org.sonarsource.sonarlint.core.analysis.container.analysis.sensor.SensorsExecutor.executeSensors(SensorsExecutor.java:93)
	at org.sonarsource.sonarlint.core.analysis.container.analysis.sensor.SensorsExecutor.execute(SensorsExecutor.java:81)
	at org.sonarsource.sonarlint.core.analysis.container.analysis.AnalysisContainer.doAfterStart(AnalysisContainer.java:122)
	at org.sonarsource.sonarlint.core.commons.tracing.Step.executeTransaction(Step.java:42)
	at org.sonarsource.sonarlint.core.commons.tracing.Trace.lambda$startChildren$0(Trace.java:76)
	at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:1024)
	at java.base/java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:762)
	at org.sonarsource.sonarlint.core.commons.tracing.Trace.startChildren(Trace.java:76)
	at org.sonarsource.sonarlint.core.plugin.commons.container.SpringComponentContainer.startComponents(SpringComponentContainer.java:183)
	at org.sonarsource.sonarlint.core.plugin.commons.container.SpringComponentContainer.execute(SpringComponentContainer.java:164)
	at org.sonarsource.sonarlint.core.analysis.container.module.ModuleContainer.analyze(ModuleContainer.java:77)
	at org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand.doRunAnalysis(AnalyzeCommand.java:198)
	at org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand.doExecute(AnalyzeCommand.java:148)
	at org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand.execute(AnalyzeCommand.java:139)
	at org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand.lambda$execute$0(AnalyzeCommand.java:131)
	at org.sonarsource.sonarlint.core.commons.progress.TaskManager.runExistingTask(TaskManager.java:47)
	at org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand.execute(AnalyzeCommand.java:130)
	at org.sonarsource.sonarlint.core.analysis.AnalysisScheduler.executeQueuedCommands(AnalysisScheduler.java:71)
	at java.base/java.lang.Thread.run(Thread.java:1583)
2

I have the exact same stacktrace in my environment (SQ EE 2026.2.1 + Adv Security)

  • Operating system: Windows 11

  • IDE name and version: Eclipse IDE for Java EE 2026-03 (4.39.0)

  • SonarQube for Eclipse plugin version: 12.1.0.84656

  • Programming language you’re coding in: Java

  • Is connected mode used: yes, SonarQube Enterprise Edition

4

Hi all,

Thanks for these reports! Since you’re in different IDEs and connected to different instances, I think this originates with the underlying analyzer. I’ve flagged this for the language experts, but it would be really helpful if you could provide some details about the code context. The commonality I see is Java. Am I correct in assuming you get this error when you’re active in a Java file?

Could you provide some details about the file? Would it be possible to boil down a minimal reproducer?

 
Thx!
Ann

5

I had a quick look at the files currently opened in my IDE, the exception only seems to appear on test files. It’s a Maven project, so basically on all files in src/test/java.

6

@ganncamp I guess I’ve found a stable reproducer.

Whenever I open ANY *.java file in the src/test/java directory subdirectories, this exception occurs.

We have a regular Maven project, with paths by convention (so src/test/java contains tests).

7

wow the same observation posted practically simutaneously)

8

Yes, crazy!!!

9

Hi,

Thanks for the followups! This is great stuff. Now that we’ve got something to go on, I’m going to go nudge the team to take a look.

 
Thx,
Ann

10

Hi again,

Just FYI, there’s a 3-day weekend involved. This should be picked up on Monday. Thanks for your (collective) patience.

 
Ann

15

Hi everyone,

DBD analyzer maintainer here! Thanks for the report: I managed to reproduce that exception in Eclipse with SonarQube for IDE.

I’m working on a fix to mitigate the problem now, and we’re also sync’ing with the IDE team to find the best way to handle this moving forward.