Running SonarQube for IDE Analysis for Java files took a long time and didn't stop:(

Please provide

  • Operating system: Windows11 24H2
  • SonarQube for IntelliJ plugin version: 10.21.0.81149
  • IntelliJ version: 2025.1 Ultimate Edition
  • Programming language you’re coding in: Java
  • Is connected mode used: No
    • SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?):

And a thorough description of the problem / question:

Analyzing the java file code took a long time and didn’t stop, it kept running

Hello @shilohooo,

Thanks for reporting here. We will need more input to be able to understand the issue. Could you try to turn on verbose logging and the next time it occurs share the logs with us.

Thanks

Hi @Damien_Urruty

I checked the link you shared but still couldn’t find a way to turn on verbose logging :joy:

After opening the IDE today, the problem seems to have gone away~

That’s weird.

SonarQubeAnalyzeTest

I had pasted the wrong link, my bad, I fixed it. Let us know if you face the problem again

1 Like

Thank you :ok_hand:

The problem has resufaced.

sonar-qube-for-ide-problem

I find the SonarQube for IDE logs here:

Analysis 491dc93d-6fb1-4025-bd85-7311ada79b45 canceled
Analysis 491dc93d-6fb1-4025-bd85-7311ada79b45 finished
Analysis canceled
Trigger: SELECTION_CHANGED
[SELECTION_CHANGED] 1 file(s) submitted
Configuring analysis with org.sonarlint.intellij.java.JavaAnalysisConfigurator
Analysing 'CloudCollectLogicSettingRel.java' (ID ccbf8059-5688-45cc-b6b6-cb2235841f7a)...
 [2025-04-25T14:25:36.708] [SonarLint Server RPC request executor] DEBUG sonarlint - Posting command in analysis queue: org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@68a6c790, new size is 13
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@584a1021, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@568df558, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@52b27b51, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@17b0ff63, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@1ff32eac, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@4773c47a, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@49b432e4, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@4d8baf0a, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@88938df, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@51006da0, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@394b5676, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@29285daa, is not ready
 [2025-04-25T14:25:36.708] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@68a6c790, is not ready
Analysis ccbf8059-5688-45cc-b6b6-cb2235841f7a canceled
Analysis ccbf8059-5688-45cc-b6b6-cb2235841f7a finished
Analysis canceled

Last 3 log lines appear after manually shutting down the analysis.

Here is the code for the analysis:

package com.sys.common.enums.cloudcollect;

import com.baomidou.mybatisplus.annotation.EnumValue;
import com.fasterxml.jackson.annotation.JsonValue;
import com.sys.common.enums.BaseEnum;
import lombok.Getter;
import lombok.RequiredArgsConstructor;

/**
 * 
 *
 * @author shiloh
 * @date 2025/4/22 16:59
 */
@Getter
@RequiredArgsConstructor
public enum CloudCollectLogicSettingRel implements BaseEnum {
    AND(1, "并且"),
    OR(2, "或者");

    @EnumValue
    @JsonValue
    private final Integer code;
    private final String desc;
}

Could you confirm this project is not connected to SonarQube Server or SonarQube Cloud?

I am having similar issues as described above with my python project with my project not connected to SonarQube server or cloud.

Ok.

Here is my SonarQube for IDE settings in IntelliJ IDEA.

Thank you for the information you shared. We are still investigating this issue and we take it seriously, it should not happen.

Could you also share whether you have multiple projects opened at the same time?

Lastly, it is happens again, it could be useful for us to take a thread dump of SonarQube for IDE and share it with us.

Thanks!

I do have multiple projects open at the same time.

I’ll provide a thread dump when the problem resurfaces.

I am having the same problem. Only one project open. Connected mode to local server at my company.

 [2025-06-18T15:13:03.182] [SonarLint Server RPC request executor] DEBUG sonarlint - Post: SonarLint Server RPC request executor 443
 [2025-06-18T15:13:03.182] [SonarLint Server RPC request executor] DEBUG sonarlint - Posting command from Scheduler: org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@a1d2b4a
 [2025-06-18T15:13:03.182] [SonarLint Server RPC request executor] DEBUG sonarlint - Posting command from Scheduler to queue: org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@a1d2b4a
 [2025-06-18T15:13:03.182] [SonarLint Server RPC request executor] DEBUG sonarlint - Posting command in analysis queue: org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@a1d2b4a, new size is 4
 [2025-06-18T15:13:03.182] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@11608ce0, is not ready
 [2025-06-18T15:13:03.182] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@224e084d, is not ready
IntelliJ IDEA 2025.1.2 (Ultimate Edition)
Build #IU-251.26094.121, built on June 3, 2025
Source revision: 616fa4675f624
Licensed to ...
Subscription is active until December 27, 2025.
Runtime version: 21.0.7+9-b895.130 amd64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.windows.WToolkit
Windows 11.0
Kotlin plugin: K2 mode
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 16384M
Cores: 28
Registry:
  analyze.exceptions.on.the.fly=true
  ide.experimental.ui=true
  jvm.dfa.analysis.ui.security.analysis.window.was.shown=true
Non-Bundled Plugins:
  com.github.deeepamin.gitlabciaid (1.11.0)
  Key Promoter X (2024.2.2)
  com.intellij.ml.llm (251.26094.80.13)
  ScriptRunner Helper (0.63)
  org.sonarlint.idea (10.25.0.81504)
  ModelDSL (1.13.2)
Kotlin: 251.26094.121-IJ

SonarQube Plugin 10.25.0.81504

threadDump-20250618-151638.txt (1.6 MB)

Hello @erikgyllenstierna and others,

Thanks for reporting here. After having a closer look, we found one situation in which the problem can occur. By any chance, do you open the same project in 2 different windows, e.g. from 2 different working copies? We have a bug in supporting this use case, where for example you clone the same repo in 2 different folders, check out different branches and open both projects in IntelliJ. Could you confirm if this is your case? If so, a fix is on the way, and should be released next Monday

2 Likes

Yes I have cloned the same repo cloned to different folders in C:. I have separate projects in IntelliJ but mostly only one open at a time. All IntelliJ projects are configured the same regarding SonarQube.

Right now I have just one IntelliJ-project open and I get one neverending SonarQube-process for each new class i open.

Trigger: SELECTION_CHANGED
[SELECTION_CHANGED] 1 file(s) submitted
Configuring analysis with org.sonarlint.intellij.java.JavaAnalysisConfigurator
Analysing 'InPaymentMessageToInPaymentConverter.java' (ID d64862a4-bec9-4fb6-8d32-039bc2e21920)...
 [2025-07-01T10:39:11.984] [SonarLint Server RPC request executor] DEBUG sonarlint - Post: SonarLint Server RPC request executor 1550
 [2025-07-01T10:39:11.984] [SonarLint Server RPC request executor] DEBUG sonarlint - Posting command from Scheduler: org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@12d09c
 [2025-07-01T10:39:11.984] [SonarLint Server RPC request executor] DEBUG sonarlint - Posting command from Scheduler to queue: org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@12d09c
 [2025-07-01T10:39:11.984] [SonarLint Server RPC request executor] DEBUG sonarlint - Posting command in analysis queue: org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@12d09c, new size is 4
 [2025-07-01T10:39:11.985] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@4115de3b, is not ready
 [2025-07-01T10:39:11.985] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@aeabbec, is not ready
 [2025-07-01T10:39:11.985] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@42d44c1, is not ready
 [2025-07-01T10:39:11.985] [sonarlint-analysis-scheduler] DEBUG sonarlint - Not picking next command org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand@12d09c, is not ready
 [2025-07-01T10:39:42.329] [SonarLint Local Storage Synchronizer] INFO sonarlint - [SYNC] Synchronizing issues for project 'se.itello.inca:inca' on branch 'master'
 [2025-07-01T10:39:42.375] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - GET 200 https://sonarqube.pcloud.lumera.com/api/issues/pull?projectKey=se.itello.inca%3Ainca&branchName=master&languages=css,web,java,js,kotlin,php,plsql,py,ruby,scala,secrets,swift,ts,xml,yaml,cloudformation,docker,kubernetes,terraform,ansible&changedSince=1751355582368 | response time=44ms
 [2025-07-01T10:39:42.375] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - Pulled issues in 44ms
 [2025-07-01T10:39:42.378] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - Merged 0 issues in store. Closed 0. | took 3ms
 [2025-07-01T10:39:42.378] [SonarLint Local Storage Synchronizer] INFO sonarlint - [SYNC] Synchronizing taint issues for project 'se.itello.inca:inca' on branch 'master'
 [2025-07-01T10:39:42.706] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - GET 200 https://sonarqube.pcloud.lumera.com/api/issues/pull_taint?projectKey=se.itello.inca%3Ainca&branchName=master&languages=css,web,java,js,kotlin,php,plsql,py,ruby,scala,secrets,swift,ts,xml,yaml,cloudformation,docker,kubernetes,terraform,ansible&changedSince=1751355582459 | response time=327ms
 [2025-07-01T10:39:42.706] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - Pulled taint issues in 327ms
 [2025-07-01T10:39:42.707] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - Merged 0 taint issues in store. Closed 0. | took 0ms
 [2025-07-01T10:39:42.708] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - Incremental hotspot sync is not supported. Skipping.
 [2025-07-01T10:39:42.71] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - isReadyForAnalysis(connectionId: Lumera, sonarProjectKey: se.itello.inca:inca, plugins: true, analyzer config: true, findings: true) => true
 [2025-07-01T10:39:42.711] [SonarLint Local Storage Synchronizer] DEBUG sonarlint - isReadyForAnalysis(connectionId: Lumera, sonarProjectKey: se.itello.inca:inca, plugins: true, analyzer config: true, findings: true) => true
Did synchronize config scopes [inca-nordeainvoicing-noninaa-war, C:/WS/core-3/Inca/Config/dev/.idea/misc.xml]
 [2025-07-01T10:39:43.862] [Smart Notifications Polling] DEBUG sonarlint - GET 200 https://sonarqube.pcloud.lumera.com/api/developers/search_events?projects=se.itello.inca%3Ainca&from=2025-07-01T10%3A38%3A43%2B0200 | response time=20ms
 [2025-07-01T10:39:43.863] [Smart Notifications Polling] DEBUG sonarlint - Storing last event polling in C:\Users\egy\AppData\Local\JetBrains\IntelliJIdea2025.1\sonarlint\storage\4c756d657261\projects\73652e6974656c6c6f2e696e63613a696e6361\last_event_polling.pb
 [2025-07-01T10:40:44.037] [Smart Notifications Polling] DEBUG sonarlint - GET 200 https://sonarqube.pcloud.lumera.com/api/developers/search_events?projects=se.itello.inca%3Ainca&from=2025-07-01T10%3A39%3A43%2B0200 | response time=203ms
 [2025-07-01T10:40:44.037] [Smart Notifications Polling] DEBUG sonarlint - Storing last event polling in C:\Users\egy\AppData\Local\JetBrains\IntelliJIdea2025.1\sonarlint\storage\4c756d657261\projects\73652e6974656c6c6f2e696e63613a696e6361\last_event_polling.pb

Thanks for confirming, the problem starts to appear if you have the 2 projects opened at the same time, and as soon as you close one of them. We will fix this for the next release

1 Like

I restarted IntelliJ using only one project and SonarQube worked perfect.

Then I opened a second project (clone of same repo) and when I press “Analyze Current File” in the second project (window) I get log output from SonarQube in both windows.

If I then close the the first or second window SonarQube runs forever in the remaining window.

So hopefully the fix will help :slight_smile:

1 Like

Hey @erikgyllenstierna, we have just released SonarQube for IntelliJ version 10.27. It includes a fix of the problem you mentioned. Could you please update and see if you still reproduce any issues?

Thank you!

1 Like

I have installed and tested 10.27. Opened several projects that are clones of the same repo and Sonar did not get “stuck” on any file anymore :slight_smile: Thanks!

4 Likes

Super, thank you for the update @erikgyllenstierna, I’m glad the issue is fixed!

If you enjoy SonarQube for IntelliJ, feel free to leave a review on our marketplace page, this is always appreciated!