Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.136 sec
------------- Standard Error -----------------
06-Feb-2024 10:07:09.933 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
06-Feb-2024 10:07:10.970 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"]
06-Feb-2024 10:07:11.021 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
06-Feb-2024 10:07:11.022 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.19-dev]
06-Feb-2024 10:07:11.315 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-42915"]
06-Feb-2024 10:07:11.593 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.
06-Feb-2024 10:07:11.609 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-42915"]
06-Feb-2024 10:07:11.611 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
06-Feb-2024 10:07:11.612 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-42915"]
06-Feb-2024 10:07:11.617 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-42915"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.049 sec