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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more