VS Code Connected Mode not working correctly

jabecker · April 14, 2025, 8:45pm

Details:

I am using version 4.20 (tried various other versions)
SonarQube server v2025.1.1
VS Code 1.99.2
Running against java code

Currently I have been having issues with SonarQube plugin running in connected mode with VS code. I am able to connect to the project from the IDE but the scanner will not run against the code and throwing the error:

[Error - 15:34:01.145] [jetbrains.exodus.env.EnvironmentImpl : SonarLint Analysis Executor] Failed to recover to valid root, address = 268631224, file = 00000008000.xd

[Error - 15:34:01.145] [jetbrains.exodus.env.EnvironmentImpl : SonarLint Analysis Executor] jetbrains.exodus.log.DataCorruptionException: DataIterator: no more bytes available, address = -1, file = 00000000000.xd

at jetbrains.exodus.log.DataCorruptionException.raise(DataCorruptionException.java:33)

at jetbrains.exodus.log.DataIterator.next(DataIterator.java:61)

at jetbrains.exodus.log.Log.readNotNull(Log.kt:481)

at jetbrains.exodus.tree.btree.BTreeBase.getLoggable(BTreeBase.java:123)

at jetbrains.exodus.tree.btree.BTreeBase.loadLeaf(BTreeBase.java:156)

at jetbrains.exodus.tree.btree.BasePageMutable.getKey(BasePageMutable.java:158)

at jetbrains.exodus.tree.btree.BasePageMutable.binarySearch(BasePageMutable.java:264)

at jetbrains.exodus.tree.btree.BasePageMutable.binarySearch(BasePageMutable.java:223)

at jetbrains.exodus.tree.btree.BasePageMutable.binarySearch(BasePageMutable.java:218)

at jetbrains.exodus.tree.btree.BottomPageMutable.put(BottomPageMutable.java:65)

at jetbrains.exodus.tree.btree.BTreeMutable.put(BTreeMutable.java:142)

at jetbrains.exodus.tree.btree.BTreeMutable.put(BTreeMutable.java:124)

at jetbrains.exodus.env.MetaTreeImpl.cloneTree(MetaTreeImpl.java:273)

at jetbrains.exodus.env.MetaTreeImpl.create(MetaTreeImpl.java:69)

at jetbrains.exodus.env.EnvironmentImpl.<init>(EnvironmentImpl.java:131)

at jetbrains.exodus.env.Environments$newInstance$4.invoke(Environments.kt:46)

at jetbrains.exodus.env.Environments$newInstance$4.invoke(Environments.kt:46)

at jetbrains.exodus.env.Environments.prepare(Environments.kt:120)

at jetbrains.exodus.env.Environments.newInstance(Environments.kt:46)

at org.sonarsource.sonarlint.core.tracking.XodusKnownFindingsStore.buildEntityStore(XodusKnownFindingsStore.java:155)

at org.sonarsource.sonarlint.core.tracking.XodusKnownFindingsStore.<init>(XodusKnownFindingsStore.java:95)

at org.sonarsource.sonarlint.core.tracking.KnownFindingsStorageService.get(KnownFindingsStorageService.java:43)

at org.sonarsource.sonarlint.core.tracking.TrackingService.startMatchingSession(TrackingService.java:266)

at org.sonarsource.sonarlint.core.tracking.TrackingService.onAnalysisStarted(TrackingService.java:107)

at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)

at java.base/java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:382)

at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:254)

at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicationEvent(ApplicationListenerMethodAdapter.java:173)

at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:185)

at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:171)

at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:156)

at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:454)

at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:400)

at org.sonarsource.sonarlint.core.analysis.AnalysisService.analyze(AnalysisService.java:658)

at org.sonarsource.sonarlint.core.analysis.AnalysisService.lambda$triggerAnalysis$46(AnalysisService.java:908)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.base/java.lang.Thread.run(Unknown Source)

ganncamp · April 16, 2025, 12:09pm

Hi,

What version of SonarQube are you connected to?

Thx,
Ann

jabecker · April 16, 2025, 4:02pm

I am connecting to a server with v2025.1.1 (104738)

I have also rolled back VS Code to 1.98.2

However, I am still receiving the error.

ganncamp · April 16, 2025, 4:37pm

Hi,

Thanks for those details. I’m going to flag this for the experts.

Ann

sophio.japharidze · April 17, 2025, 1:16pm

Hello @jabecker,

Thanks for the report!! The error message from the logs indicate that for some reason the SonarQube for IDE issue storage has been corrupted

To fix this, you can try removing the
$HOME/.sonarlint/known-findings-store-*
$HOME/.sonarlint/.sonarlinttmp*
$HOME/.sonarlint/storage/local_only_issues_backup.tar.gz
folders and reloading the IDE window.

Hope this helps,
Sophio

jabecker · April 18, 2025, 2:03pm

Thank you so much that cleared up my issue

Topic		Replies	Views
Issues no longer appear VS Code	2	131	February 21, 2025
Add sonarqube connection is not working in vs code VS Code	10	1384	July 10, 2023
SonarLint for VSCode can't connect to SonarQube VS Code sonarqube , connected_mode	1	1064	March 13, 2023
Connected Mode not working with VS Code SonarLint and Sonarqube SonarQube Server / Community Build sonarqube-ide	3	20	July 26, 2024
Connected mode seemingly doesn't work 🤔 VS Code connected_mode , sonarqube-ide , sonarqube-cloud	3	1425	May 4, 2023

VS Code Connected Mode not working correctly

Related topics