Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.905 sec
------------- Standard Error -----------------
09-Nov-2024 09:48:23.372 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
09-Nov-2024 09:48:24.456 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"]
09-Nov-2024 09:48:24.494 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
09-Nov-2024 09:48:24.495 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.34-dev]
09-Nov-2024 09:48:24.888 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-38169"]
09-Nov-2024 09:48:25.051 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.
09-Nov-2024 09:48:25.061 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-38169"]
09-Nov-2024 09:48:25.073 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
09-Nov-2024 09:48:25.075 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-38169"]
09-Nov-2024 09:48:25.080 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-38169"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 1.824 sec