Testsuite: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.503 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-4] EXITING class java.lang.Thread [pool-1-thread-3] EXITING class java.lang.Thread [pool-1-thread-1] EXITING ------------- ---------------- --------------- ------------- Standard Error ----------------- 24-Oct-2024 16:45:27.924 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak] 24-Oct-2024 16:45:29.350 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"] 24-Oct-2024 16:45:29.523 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat] 24-Oct-2024 16:45:29.523 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.32-dev] 24-Oct-2024 16:45:29.732 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36683"] 24-Oct-2024 16:45:30.073 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.12/java.lang.Thread.sleep(Native Method) app//org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:120) java.base@17.0.12/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) java.base@17.0.12/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) java.base@17.0.12/java.lang.Thread.run(Thread.java:840) 24-Oct-2024 16:45:30.079 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.12/java.lang.Thread.sleep(Native Method) app//org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:120) java.base@17.0.12/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) java.base@17.0.12/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) java.base@17.0.12/java.lang.Thread.run(Thread.java:840) 24-Oct-2024 16:45:30.099 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36683"] 24-Oct-2024 16:45:30.103 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat] 24-Oct-2024 16:45:30.105 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36683"] 24-Oct-2024 16:45:30.113 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36683"] ------------- ---------------- --------------- Testcase: testTimerThreadLeak took 2.378 sec