Testsuite: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.167 sec
------------- Standard Output ---------------
class java.lang.Thread [pool-1-thread-3] EXITING
class java.lang.Thread [pool-1-thread-5] EXITING
class java.lang.Thread [pool-1-thread-4] EXITING
class java.lang.Thread [pool-1-thread-1] EXITING
class java.lang.Thread [pool-1-thread-2] EXITING
------------- ---------------- ---------------
------------- Standard Error -----------------
12-Dec-2023 18:02:45.683 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
12-Dec-2023 18:02:46.885 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
12-Dec-2023 18:02:47.070 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
12-Dec-2023 18:02:47.071 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.85-dev]
12-Dec-2023 18:02:47.266 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-37213"]
12-Dec-2023 18:02:47.511 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@17.0.7/java.lang.Thread.sleep(Native Method)
 app//org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:120)
 java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
 java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 java.base@17.0.7/java.lang.Thread.run(Thread.java:833)
12-Dec-2023 18:02:47.513 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@17.0.7/java.io.Writer.write(Writer.java:249)
 java.base@17.0.7/java.io.PrintStream.writeln(PrintStream.java:720)
 java.base@17.0.7/java.io.PrintStream.println(PrintStream.java:1028)
 app//org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:125)
 java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
 java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 java.base@17.0.7/java.lang.Thread.run(Thread.java:833)
12-Dec-2023 18:02:47.519 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-37213"]
12-Dec-2023 18:02:47.521 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
12-Dec-2023 18:02:47.523 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-37213"]
12-Dec-2023 18:02:47.525 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-37213"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.079 sec