SonarQube for IDE 11.26 - Eclipse Plugin - Throws Exception when doubleclicking in Report-List

SonarQube for IDE Eclipse
1

Please provide

  • Windows
  • Eclipse 2025-12
  • SonarQube for Eclipse plugin version: 11.26
  • Programming language you’re coding in: JAVA
  • Is connected mode used: SonarQube Server
    *

We have a project “ GitHub - SVWS-NRW/SVWS-Server: OpenSource Repository für den SVWS-Server ”.

  • Rightclick on folder “svws-core” –> SonarQube –> Analyze
  • Waiting, then SonarQube Report has 2791 items.
  • “Wild” doubleclicking on several Elements/Descriptions causes Exception, but only sometimes. You can see the “Progress Area” the process “fetching rule description for …”
  • After several wild clicks I get (sometimes its enough if you work fast and want to jump from element to element):
    org.sonarsource.sonarlint.shaded.org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Failed to retrieve finding details. Finding with key ‘a6af6fa0-53af-47ff-bf59-2c9e9cbff163’ not found.

My analysis so far is, that it seldom happens, when the PC is not busy (My PC is an AMD Ryzen 9 5950X 16-Core).

But at the moment I have 16 Virtual Machines Running in the Background with quite some load. This leads to a much more higher chance of triggering an Exception. So I think there is some snychronization problems when doubleclicking from element to element.

Sincerely

Benjamin Bartsch

2

Hi Benjamin,

Could we get a verbose log from IDE startup through to this error?

 
Thx!
Ann

3

VerboseClickReport.txt (189.8 KB)

5

Hi,

Thanks for the log! I’ve flagged this for the team.

 
Ann

7

One addition: Its also happening when:

  • I doubleclick on an issue (I mean a row in the report table)
  • Then I resolve the Issue
  • Then I save. Sometimes the Issue ist now removed from list, but not always.
  • If its not removed from list and I then doubleclick the Issue an Exception is thrown.
9

Hi @benjaminbartsch,

Thanks for reporting, and sorry for the very late answer. I can see indeed a race condition that can occur in this case:

  • analyze some files and have issues displayed
  • trigger a new analysis on one of the files that has an issue (e.g. by opening the file, or analyzing the project)
  • quickly double click on an existing issue before the analysis is over

I created this ticket: Jira

The workaround is normally to wait for the end of the ongoing analysis.

Just to be transparent, we have other priorities at the moment, so it’s unlikely this will be fixed anytime soon.

Thanks again!