Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.21 sec
------------- Standard Error -----------------
22-Jan-2024 16:05:06.311 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
22-Jan-2024 16:05:07.352 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
22-Jan-2024 16:05:07.450 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
22-Jan-2024 16:05:07.450 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.19-dev]
22-Jan-2024 16:05:07.656 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42937"]
22-Jan-2024 16:05:07.881 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.
22-Jan-2024 16:05:07.890 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42937"]
22-Jan-2024 16:05:07.892 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
22-Jan-2024 16:05:07.906 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42937"]
22-Jan-2024 16:05:07.910 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42937"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.1 sec