Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.462 sec
------------- Standard Error -----------------
14-Jun-2024 18:48:56.278 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
14-Jun-2024 18:48:57.528 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
14-Jun-2024 18:48:57.710 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
14-Jun-2024 18:48:57.711 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.25-dev]
14-Jun-2024 18:48:57.900 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41449"]
14-Jun-2024 18:48:58.091 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.
14-Jun-2024 18:48:58.119 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41449"]
14-Jun-2024 18:48:58.125 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
14-Jun-2024 18:48:58.126 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41449"]
14-Jun-2024 18:48:58.129 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41449"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.328 sec