Startup error with the findbugs plugin since 2025.3

SonarQube Server / Community Build Plugin Development
1

Hello,
After upgrading to SonarQube 2025.3 users are reporting a startup error with the findbugs plugin, as reported here:

2025.06.02 18:16:31 ERROR web[][o.s.s.p.Platform] Background initialization failed. Stopping SonarQube
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@5ffd2b27-org.sonar.server.qualityprofile.builtin.BuiltInQProfileLoader': The following languages have no built-in quality profiles: kubernetescssscalajsppyjsansibledockerplsqlrustdartjavawebflexxmljsonipynbtextvbnetcloudformationgrvyyamlswiftcppcgokotlinneutraltsqlsecretsrubycsshellphpterraformazureresourcemanagerabapobjcts
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:614)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:529)
        at ...
org.sonar.server.platform.PlatformImpl$AutoStarterRunnable.run(PlatformImpl.java:349)
        at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.IllegalStateException: The following languages have no built-in quality profiles: kubernetescssscalajsppyjsansibledockerplsqlrustdartjavawebflexxmljsonipynbtextvbnetcloudformationgrvyyamlswiftcppcgokotlinneutraltsqlsecretsrubycsshellphpterraformazureresourcemanagerabapobjcts
        at com.google.common.base.Preconditions.checkState(Preconditions.java:603)
        at org.sonar.server.qualityprofile.builtin.BuiltInQProfileRepositoryImpl.ensureAllLanguagesHaveAtLeastOneBuiltInQP(BuiltInQProfileRepositoryImpl.java:108)
        at org.sonar.server.qualityprofile.builtin.BuiltInQProfileRepositoryImpl.initialize(BuiltInQProfileRepositoryImpl.java:90)
        at org.sonar.server.qualityprofile.builtin.BuiltInQProfileLoader.start(BuiltInQProfileLoader.java:37)

I have created a small PR for the garbled error message, but I’m still not sure what might be going on.

The plugin handles the following languages: java, JSP, scala, clojure, kotlin. Could it be that a built-in quality profile was removed and now the findbugs plugin needs to provide the default quality profile?

It is complicated to debug this because it only seems to happen on the latest commercial version (2025.3) while the 25.5 community server works fine. Unfortunately I do not have access to a commercial edition of SonarQube.

There seem to be a 25.6 version here but I do not see it on maven here.

I’m used to try out the latest community server with integration tests spinning up an instance with Orchestrator, but this time around it looks like the community version was lagging in some aspects compared to the commercial editions.

2

Hey @gtoison

For what it’s worth, nothing should stop you from downloading a commercial edition Download SonarQube and even starting it up. You just won’t be able to run analyses, and that’s not what’s failing (if I understand correctly, the startup is failing).

I’ll dig into this on my side to see if I can find something obvious that has changed “between” 25.5 and 2025.3.

3

In any case there’s very clearly a bug because this:

Is simply not correct (and thanks for the PR). I will flag this for the team.

5

Thanks for the prompt answers Colin, it’s good to know that I can experiment with a commercial edition!

6

Hello @dmeneses
Sorry to ping you here but I think you might be the Spring expert around here!

This is to let you know that the problem was because the plugin quality profiles had unresolved dependencies: their constructor injected the profile importer and I had disabled it because importers are now gone.
I’m not sure exactly why, but this resulted in BuiltInQProfileRepositoryImpl being initialized with its first constructor (without the QP definitions).
Since it had no quality profiles, it was throwing that confusing error message.

Fixing the missing injection dependency in the plugin solved the problem.