Increased scanning time using Java 25

SonarQube Server / Community Build
,
1

Hello,

We are currently using SonarQube Server version 2025.4.7 deployed with Docker.

We are upgrading SonarQube Server from 2025.4.7 to 2026.1 LTA. In preparation for the upgrade, we updated the sonar-scanner step in our Bitbucket pipelines to use Java 25 (image: maven:3.9-eclipse-temurin-25).

On SonarQube Server 2025.4.7, the scan took 9 minutes with Java 17 and Java 21 but increased to 20 minutes with Java 25.

Is there any insight into why the scan takes significantly longer with Java 25? Also, do SonarQube Server 2025.4.7 and 2026.1 LTA versions support Java 25?

Thank you.

2

Hey @Suzanne_Fuller, welcome to the Community!

On SonarQube Server 2025.4.7, the scan took 9 minutes with Java 17 and Java 21 but increased to 20 minutes with Java 25.

Do you mean that the scan takes 9 mins with Java 17/21 on SonarQube 2025.4 and 20 mins with Java 25 on SonarQube 2026.1? Or did you get the 20-min-long analyses on SonarQube Server 2025.4.7 too, just by changing the Java version?

In principle, 2025.4 is documented as supporting Java 17 and 21, while 2026.1 is documented as supporting Java 21 and 25. I would recommend to follow those requirements.

3

Thank you for the recommendation. We will update to Java 25 after upgrading to 2026.1.