Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.442 sec
------------- Standard Error -----------------
05-Feb-2024 10:01:49.551 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
05-Feb-2024 10:01:50.695 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
05-Feb-2024 10:01:50.827 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
05-Feb-2024 10:01:50.828 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.19-dev]
05-Feb-2024 10:01:51.016 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41047"]
05-Feb-2024 10:01:51.216 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-Feb-2024 10:01:51.222 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41047"]
05-Feb-2024 10:01:51.246 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
05-Feb-2024 10:01:51.247 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41047"]
05-Feb-2024 10:01:51.250 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41047"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.329 sec