Testsuite: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.08 sec
------------- Standard Output ---------------
class java.lang.Thread [pool-1-thread-5] EXITING
class java.lang.Thread [pool-1-thread-2] EXITING
class java.lang.Thread [pool-1-thread-3] EXITING
class java.lang.Thread [pool-1-thread-4] EXITING
class java.lang.Thread [pool-1-thread-1] EXITING
------------- ---------------- ---------------
------------- Standard Error -----------------
20-Sep-2024 14:46:31.282 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
20-Sep-2024 14:46:32.463 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
20-Sep-2024 14:46:32.575 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
20-Sep-2024 14:46:32.576 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.31-dev]
20-Sep-2024 14:46:32.762 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-46701"]
20-Sep-2024 14:46:33.018 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)
20-Sep-2024 14:46:33.021 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-1-thread-3] 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.StringCoding.implEncodeAsciiArray(StringCoding.java:65)
 java.base@17.0.7/java.lang.System$2.encodeASCII(System.java:2414)
 java.base@17.0.7/sun.nio.cs.UTF_8$Encoder.encodeArrayLoop(UTF_8.java:456)
 java.base@17.0.7/sun.nio.cs.UTF_8$Encoder.encodeLoop(UTF_8.java:564)
 java.base@17.0.7/java.nio.charset.CharsetEncoder.encode(CharsetEncoder.java:585)
 java.base@17.0.7/sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:293)
 java.base@17.0.7/sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
 java.base@17.0.7/sun.nio.cs.StreamEncoder.write(StreamEncoder.java:132)
 java.base@17.0.7/java.io.OutputStreamWriter.write(OutputStreamWriter.java:205)
 java.base@17.0.7/java.io.BufferedWriter.flushBuffer(BufferedWriter.java:120)
 java.base@17.0.7/java.io.PrintStream.writeln(PrintStream.java:722)
 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)
20-Sep-2024 14:46:33.033 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-46701"]
20-Sep-2024 14:46:33.037 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
20-Sep-2024 14:46:33.041 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-46701"]
20-Sep-2024 14:46:33.043 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-46701"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 1.944 sec