Testsuite: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.035 sec ------------- Standard Output --------------- 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-3] EXITING class java.lang.Thread [pool-1-thread-2] EXITING class java.lang.Thread [pool-1-thread-1] EXITING ------------- ---------------- --------------- ------------- Standard Error ----------------- 28-Jun-2024 13:36:42.435 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak] 28-Jun-2024 13:36:43.453 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"] 28-Jun-2024 13:36:43.601 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat] 28-Jun-2024 13:36:43.601 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.26-dev] 28-Jun-2024 13:36:43.891 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33251"] 28-Jun-2024 13:36:44.166 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) 28-Jun-2024 13:36:44.170 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.lang.Throwable.(Throwable.java:270) java.base@17.0.7/java.lang.Exception.(Exception.java:67) java.base@17.0.7/java.lang.InterruptedException.(InterruptedException.java:67) 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) 28-Jun-2024 13:36:44.176 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33251"] 28-Jun-2024 13:36:44.190 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat] 28-Jun-2024 13:36:44.199 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33251"] 28-Jun-2024 13:36:44.203 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33251"] ------------- ---------------- --------------- Testcase: testTimerThreadLeak took 1.927 sec