Quantcast
Channel: XWiki Forum - Latest topics
Viewing all articles
Browse latest Browse all 1220

The web application [xwiki] appears to have started a thread named [non-blocking-thread--p2-t8] but has failed to stop it. This is very likely to create a memory leak

$
0
0

XWiki 16 + PSQL
Running on Debian
Using Tomcat9
Hello, I’m seeing this on my Tomcat logs, should I worry?

04-Dec-2024 12:15:25.420 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [xwiki] appears to have started a thread named [non-blocking-thread--p2-t8] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@17.0.13/jdk.internal.misc.Unsafe.park(Native Method)
 java.base@17.0.13/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
 java.base@17.0.13/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
 java.base@17.0.13/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3465)
 java.base@17.0.13/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3436)
 java.base@17.0.13/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1630)
 java.base@17.0.13/java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:435)
 java.base@17.0.13/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
 java.base@17.0.13/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
 java.base@17.0.13/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)

If so, how do I fix it or mitigate it?

Attached is my logfile.
catalina.2024-12-04.log (245.5 KB)

4 posts - 3 participants

Read full topic


Viewing all articles
Browse latest Browse all 1220

Trending Articles