Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.013 sec ------------- Standard Error ----------------- 15-Nov-2024 14:51:40.653 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak] 15-Nov-2024 14:51:41.757 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"] 15-Nov-2024 14:51:41.908 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat] 15-Nov-2024 14:51:41.908 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.34-dev] 15-Nov-2024 14:51:42.153 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-39803"] 15-Nov-2024 14:51:42.383 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesStopTimerThread The web application [ROOT] appears to have started a TimerThread named [leaked-thread] via the java.util.Timer API but has failed to stop it. To prevent a memory leak, the timer (and hence the associated thread) has been forcibly canceled. 15-Nov-2024 14:51:42.396 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-39803"] 15-Nov-2024 14:51:42.402 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat] 15-Nov-2024 14:51:42.403 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-39803"] 15-Nov-2024 14:51:42.406 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-39803"] ------------- ---------------- --------------- Testcase: testTimerThreadLeak took 1.925 sec