Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.362 sec
------------- Standard Error -----------------
25-Nov-2024 12:53:19.424 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
25-Nov-2024 12:53:20.855 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
25-Nov-2024 12:53:21.029 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
25-Nov-2024 12:53:21.030 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.34-dev]
25-Nov-2024 12:53:21.248 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42099"]
25-Nov-2024 12:53:21.389 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.
25-Nov-2024 12:53:21.410 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42099"]
25-Nov-2024 12:53:21.413 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
25-Nov-2024 12:53:21.416 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42099"]
25-Nov-2024 12:53:21.431 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42099"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.212 sec