Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.273 sec
------------- Standard Error -----------------
05-Nov-2024 18:16:49.175 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
05-Nov-2024 18:16:50.673 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"]
05-Nov-2024 18:16:50.713 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
05-Nov-2024 18:16:50.714 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.32-dev]
05-Nov-2024 18:16:50.883 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-36681"]
05-Nov-2024 18:16:51.135 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.
05-Nov-2024 18:16:51.154 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-36681"]
05-Nov-2024 18:16:51.159 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
05-Nov-2024 18:16:51.160 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-36681"]
05-Nov-2024 18:16:51.168 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-36681"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.152 sec