SonarQube 2026.1.0 instance restarting due to some slack API

We have upgraded our SonarQube instance from 2025.1.4 to 2026.1.0 and since then we have observed that our instance is restarting during projects scanning with below error.FYI we are not using ay slack related APIs .

2026-03-26T11:54:01.351+05:30 2026.03.26 06:24:01 WARN web[][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [slack-api-metrics:563daeed-worker-51] 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:269)\n java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1797)\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\n java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1070)\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)

Hi,

Thanks for this report.

Please provide the few lines before the error and the full stacktrace.

 
Thx,
Ann

PFB logs :

2026-03-26T14:28:07.790+05:30
2026.03.26 08:58:07 INFO ce[d20de506-0d5f-4e48-bf94-aab9d8125908][o.s.c.t.s.ComputationStepExecutor] Build tree of components | components=8 | status=SUCCESS | time=5ms
2026-03-26T14:28:07.794+05:30
2026.03.26 08:58:07 INFO ce[d20de506-0d5f-4e48-bf94-aab9d8125908][o.s.c.t.s.ComputationStepExecutor] Validate project | status=SUCCESS | time=3ms
2026-03-26T14:28:10.087+05:30
2026.03.26 08:58:10 WARN app[ ][o.s.a.p.AbstractManagedProcess] Process exited with exit value [Compute Engine]: 137
2026-03-26T14:28:10.087+05:30
2026.03.26 08:58:10 INFO app[ ][o.s.a.SchedulerImpl] Process[Compute Engine] is stopped
2026-03-26T14:28:10.577+05:30
2026.03.26 08:58:10 INFO web[ ][o.s.p.ProcessEntryPoint] Hard stopping process
2026-03-26T14:28:10.603+05:30
2026.03.26 08:58:10 INFO web[ ][o.s.s.e.CoreExtensionStopper] Stopping Governance
2026-03-26T14:28:10.603+05:30
2026.03.26 08:58:10 INFO web[ ][o.s.s.e.CoreExtensionStopper] Stopping Governance (done) | time=0ms
2026-03-26T14:28:10.604+05:30
2026.03.26 08:58:10 INFO web[ ][o.s.s.n.NotificationDaemon] Notification service stopped
2026-03-26T14:28:10.647+05:30
2026.03.26 08:58:10 INFO web[ ][c.z.h.HikariDataSource] HikariPool-1 - Shutdown initiated…
2026-03-26T14:28:10.651+05:30
2026.03.26 08:58:10 INFO web[ ][c.z.h.HikariDataSource] HikariPool-1 - Shutdown completed.
2026-03-26T14:28:10.655+05:30
2026.03.26 08:58:10 WARN web[ ][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [slack-api-metrics:31604f33-worker-44] 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:269)\n java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1797)\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\n java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1070)\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)
2026-03-26T14:28:10.656+05:30
2026.03.26 08:58:10 WARN web[ ][o.a.c.l.WebappClassLoaderBase] The web application [ROOT] appears to have started a thread named [slack-api-metrics:792726f3-worker-45] 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:269)\n java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1797)\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\n java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1070)\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)

Hi,

This log isn’t terribly helpful. It’s an aggregate log and doesn’t include the error or its stacktrace.

Please take a look at your server logs and share the relevant one, starting from a few lines before the error and continuing through the end of the stacktrace.

 
Ann

Error is clearly mentioned at the end of the logs but still please find below logs which may help :

2026-03-26T14:28:07.790+05:30
2026.03.26 08:58:07 INFO ce\[d20de506-0d5f-4e48-bf94-aab9d8125908\]\[o.s.c.t.s.ComputationStepExecutor\] Build tree of components | components=8 | status=SUCCESS | time=5ms
2026-03-26T14:28:07.794+05:30
2026.03.26 08:58:07 INFO ce\[d20de506-0d5f-4e48-bf94-aab9d8125908\]\[o.s.c.t.s.ComputationStepExecutor\] Validate project | status=SUCCESS | time=3ms
2026-03-26T14:28:10.087+05:30
2026.03.26 08:58:10 WARN app[ ]\[o.s.a.p.AbstractManagedProcess\] Process exited with exit value \[Compute Engine\]: 137
2026-03-26T14:28:10.087+05:30
2026.03.26 08:58:10 INFO app[ ]\[o.s.a.SchedulerImpl\] Process\[Compute Engine\] is stopped
2026-03-26T14:28:10.577+05:30
2026.03.26 08:58:10 INFO web[ ]\[o.s.p.ProcessEntryPoint\] Hard stopping process
2026-03-26T14:28:10.603+05:30
2026.03.26 08:58:10 INFO web[ ]\[o.s.s.e.CoreExtensionStopper\] Stopping Governance
2026-03-26T14:28:10.603+05:30
2026.03.26 08:58:10 INFO web[ ]\[o.s.s.e.CoreExtensionStopper\] Stopping Governance (done) | time=0ms
2026-03-26T14:28:10.604+05:30
2026.03.26 08:58:10 INFO web[ ]\[o.s.s.n.NotificationDaemon\] Notification service stopped
2026-03-26T14:28:10.647+05:30
2026.03.26 08:58:10 INFO web[ ]\[c.z.h.HikariDataSource\] HikariPool-1 - Shutdown initiated…
2026-03-26T14:28:10.651+05:30
2026.03.26 08:58:10 INFO web[ ]\[c.z.h.HikariDataSource\] HikariPool-1 - Shutdown completed.
2026-03-26T14:28:10.655+05:30
2026.03.26 08:58:10 WARN web[ ]\[o.a.c.l.WebappClassLoaderBase\] The web application \[ROOT\] appears to have started a thread named \[slack-api-metrics:31604f33-worker-44\] 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:269)\\n java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1797)\\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)\\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\\n java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1070)\\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)
2026-03-26T14:28:10.656+05:30
WARN web[ ]\[o.a.c.l.WebappClassLoaderBase\] The web application \[ROOT\] appears to have started a thread named \[slack-api-metrics:792726f3-worker-45\] 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:269)\\n java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1797)\\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)\\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\\n java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1070)\\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)*

*2026.03.26 08:58:10 WARN web[ ]\[o.a.c.l.WebappClassLoaderBase\] The web application \[ROOT\] appears to have started a thread named \[slack-api-metrics:563daeed-worker-51\] 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:269)\\n java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:1797)\\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)\\n java.base/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)\\n java.base/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1070)\\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)

Hi,

Again (emphasis added)

This

is not the error. It’s the outcome.

I need you to find ce.log and provide the underlying error and its stacktrace.

 
Ann

Anyways we found issue and resolved the same and now it is working fine !
Thanks.