Must-share information (formatted with Markdown):
- SonarQube Enterprise 2025.3.0
- Deployed from Helm (sonarqube 2025.3.0 Β· sonarsource/sonarqube) into EKS
SonarQube is running properly but every 30secs there is a null pointer exception in the logs, even on empty installation with no projects.
2025.06.16 09:44:28 WARN web[][o.s.s.m.MainCollector] Error while executing monitoring task in RecentTasksDurationTask: β
β java.lang.NullPointerException: at index 0 β
β at com.google.common.collect.ObjectArrays.checkElementNotNull(ObjectArrays.java:232) β
β at com.google.common.collect.ObjectArrays.checkElementsNotNull(ObjectArrays.java:222) β
β at com.google.common.collect.ObjectArrays.checkElementsNotNull(ObjectArrays.java:216) β
β at com.google.common.collect.ImmutableList.sortedCopyOf(ImmutableList.java:345) β
β at com.google.common.collect.Ordering.immutableSortedCopy(Ordering.java:899) β
β at org.sonar.db.DatabaseUtils.toUniqueAndSortedList(DatabaseUtils.java:204) β
β at org.sonar.db.DatabaseUtils.toUniqueAndSortedPartitions(DatabaseUtils.java:190) β
β at org.sonar.db.DatabaseUtils.executeLargeInputs(DatabaseUtils.java:139) β
β at org.sonar.db.DatabaseUtils.executeLargeInputs(DatabaseUtils.java:125) β
β at org.sonar.db.DatabaseUtils.executeLargeInputs(DatabaseUtils.java:114) β
β at org.sonar.db.entity.EntityDao.selectByUuids(EntityDao.java:42) β
β at org.sonar.server.monitoring.ce.RecentTasksDurationTask.run(RecentTasksDurationTask.java:60) β
β at org.sonar.server.monitoring.MainCollector.lambda$start$0(MainCollector.java:54) β
β at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) β
β at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source) β
β at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) β
β 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)
The error does not seem to impact functionality (at least not spotted) but creates noise in the monitoring tools.