Warnings /exceptions during SonarQube 2025.1.4 upgrade

SonarQube Server / Community Build
1

when migrating to 2025.1.4 LTA from 9.9.9 LTA , we observed below 4 warnings/exception. ,anything serious or we skipped anything ? Kindly assist.

1.

2025-11-21T11:27:40.772+05:30
2025.11.21 05:57:40 WARN ce[o.s.c.a.AnnotationConfigApplicationContext] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘jdk.internal.loader.ClassLoaders$AppClassLoader@497470ed-org.sonar.ce.container.CePluginRepository’: Fail to unzip plugin [detekt] /opt/sonarqube/extensions/plugins/sonar-detekt-2.5.0.jar to /opt/sonarqube/temp/ce-exploded-plugins/detect

2.

Caused by: java.lang.IllegalStateException: Fail to unzip plugin [detekt] /opt/sonarqube/extensions/plugins/sonar-detekt-2.5.0.jar to /opt/sonarqube/temp/ce-exploded-plugins/detect

3.

2025-11-21T11:27:40.833+05:30
Caused by: java.io.IOException: Cannot allocate memory

4.

2025-11-21T11:27:41.367+05:30
2025.11.21 05:57:41 WARN web[o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [OkHttp TaskRunner] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:\n java.base/jdk.internal.misc.Unsafe.park(Native Method)\n java.base/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:410)\n java.base/java.util.concurrent.LinkedTransferQueue$DualNode.await(LinkedTransferQueue.java:452)\n java.base/java.util.concurrent.SynchronousQueue$Transferer.xferLifo(SynchronousQueue.java:194)\n java.base/java.util.concurrent.SynchronousQueue.xfer(SynchronousQueue.java:235)\n java.base/java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:338)\n java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1069)\n java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)\n java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)\n java.base/java.lang.Thread.run(Thread.java:1583)

2

Hey there.

#1 and #2 seem related to the archived GitHub - detekt/sonar-detekt: SonarQube plugin for Kotlin plugin. You shouldn’t need this plugin since you can import Detekt reports as external issues

#3 and #4, without more context (a complete logfile), I couldn’t say.

3

That means we cant use that plugin anymore ?

any code or setting need to change at application side for scanning code which using kotlin?

4

Hi,

Why would you want to? It’s a native feature now.

 
HTH,
Ann