Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.281 sec
------------- Standard Error -----------------
15-Jan-2024 15:39:11.073 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
15-Jan-2024 15:39:12.386 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"]
15-Jan-2024 15:39:12.447 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
15-Jan-2024 15:39:12.447 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.86-dev]
15-Jan-2024 15:39:12.620 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-39399"]
15-Jan-2024 15:39:12.800 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.
15-Jan-2024 15:39:12.806 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-39399"]
15-Jan-2024 15:39:12.811 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
15-Jan-2024 15:39:12.812 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-39399"]
15-Jan-2024 15:39:12.827 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-39399"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.191 sec