Skip to main content

SonarQube on Windows Troubleshooting

After installing a new SonarQube version on one our Windows Server VM’s, I encountered some issues. Let me walk you through the problems I encountered and how I fixed them.

Issue 1 -  java.lang.UnsupportedClassVersionError

After I extracted the SonarQube binaries I opened the installation folder, went to the bin\windows-x86-64 folder and tried to run the startsonar.bat file. This failed with the following error message:

D:\sonar\bin\windows-x86-64>startsonar

Starting SonarQube...

Error: LinkageError occurred while loading main class org.sonar.application.App

        java.lang.UnsupportedClassVersionError: org/sonar/application/App has been compiled by a more recent version of the Java Runtime (class file version 61.0), this version of the Java Runtime only recognizes class file versions up to 55.0

The error above is related to the class file version. Each JDK release comes with its class file version. Class files are backward compatible but files compiled for newer JDK releases cannot be executed and will result in an UnsupportedClassVersionError as I learned here.

So I needed a least Java 17 to make SonarQube work.

I wanted to avoid the Oracle JDK (due to their license changes) and decided to install the Microsoft build of the OpenJDK.  Yes, Microsoft made their own build of the OpenJDK.

I downloaded and installed the latest version(because the latest version is always better right?).

As a last step I updated the SONAR_JAVA_PATH variable to point to this new installation:

setx SONAR_JAVA_PATH "C:\Program Files\Microsoft\jdk-21.0.3\bin\java.exe"

 

Issue 2 - java.lang.UnsupportedOperationException

Now when I tried to run SonarQube, it failed again however with a different error message:

Exception in thread "main" java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release

at java.base/java.lang.System.setSecurityManager(System.java:430)

at org.sonar.process.PluginSecurityManager.restrictPlugins(PluginSecurityManager.java:42)

at org.sonar.server.app.WebSecurityManager.apply(WebSecurityManager.java:47)

at org.sonar.server.app.WebServer.main(WebServer.java:101)

Turns out that SonarQube is using a feature that was marked deprecated in Java 17 and was removed in Java 21. So I uninstalled the OpenJDK 21 and instead installed the OpenJDK 17 version.

Don’t forget to update the path:

setx SONAR_JAVA_PATH "C:\Program Files\Microsoft\jdk-17.0.11\bin\java.exe"

More information

Download the Microsoft Build of OpenJDK | Microsoft Learn

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more