Testsuite: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.467 sec
------------- Standard Output ---------------
class java.lang.Thread [pool-1-thread-3] EXITING
class java.lang.Thread [pool-1-thread-1] EXITING
class java.lang.Thread [pool-1-thread-2] EXITING
class java.lang.Thread [pool-1-thread-5] EXITING
class java.lang.Thread [pool-1-thread-4] EXITING
------------- ---------------- ---------------
------------- Standard Error -----------------
10-Oct-2023 20:20:15.762 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
10-Oct-2023 20:20:17.010 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
10-Oct-2023 20:20:17.140 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
10-Oct-2023 20:20:17.140 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/8.5.95-dev]
10-Oct-2023 20:20:17.396 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-43733"]
10-Oct-2023 20:20:17.661 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-1-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@11.0.16.1/java.lang.Thread.sleep(Native Method)
 app//org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:120)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 java.base@11.0.16.1/java.lang.Thread.run(Thread.java:829)
10-Oct-2023 20:20:17.667 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-1-thread-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@11.0.16.1/java.lang.Thread.currentThread(Native Method)
 java.base@11.0.16.1/java.util.concurrent.locks.ReentrantLock$Sync.nonfairTryAcquire(ReentrantLock.java:127)
 java.base@11.0.16.1/java.util.concurrent.locks.ReentrantLock$NonfairSync.tryAcquire(ReentrantLock.java:199)
 java.base@11.0.16.1/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1239)
 java.base@11.0.16.1/java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:267)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:986)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 java.base@11.0.16.1/java.lang.Thread.run(Thread.java:829)
10-Oct-2023 20:20:17.669 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-1-thread-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@11.0.16.1/java.io.PrintStream.println(PrintStream.java:882)
 app//org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:125)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 java.base@11.0.16.1/java.lang.Thread.run(Thread.java:829)
10-Oct-2023 20:20:17.670 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-1-thread-5] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@11.0.16.1/java.io.PrintStream.println(PrintStream.java:882)
 app//org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:125)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 java.base@11.0.16.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 java.base@11.0.16.1/java.lang.Thread.run(Thread.java:829)
10-Oct-2023 20:20:17.701 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-43733"]
10-Oct-2023 20:20:17.703 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
10-Oct-2023 20:20:17.713 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-43733"]
10-Oct-2023 20:20:17.715 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-43733"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.322 sec