Testsuite: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.288 sec ------------- Standard Output --------------- class java.lang.Thread [pool-1-thread-5] EXITING class java.lang.Thread [pool-1-thread-3] 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-1] EXITING ------------- ---------------- --------------- ------------- Standard Error ----------------- 22-Mar-2024 13:14:15.087 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak] 22-Mar-2024 13:14:16.191 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"] 22-Mar-2024 13:14:16.390 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat] 22-Mar-2024 13:14:16.391 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.21-dev] 22-Mar-2024 13:14:16.543 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-34369"] 22-Mar-2024 13:14:16.859 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) 22-Mar-2024 13:14:16.862 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.util.HashMap$HashIterator.(HashMap.java:1585) java.base@17.0.7/java.util.HashMap$KeyIterator.(HashMap.java:1618) java.base@17.0.7/java.util.HashMap$KeySet.iterator(HashMap.java:983) java.base@17.0.7/java.util.HashSet.iterator(HashSet.java:174) java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor.interruptIdleWorkers(ThreadPoolExecutor.java:795) java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor.tryTerminate(ThreadPoolExecutor.java:716) java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:1002) java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1150) 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) 22-Mar-2024 13:14:16.868 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-34369"] 22-Mar-2024 13:14:16.870 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat] 22-Mar-2024 13:14:16.871 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-34369"] 22-Mar-2024 13:14:16.875 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-34369"] ------------- ---------------- --------------- Testcase: testTimerThreadLeak took 2.201 sec