Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.491 sec
------------- Standard Error -----------------
05-Feb-2024 15:34:08.225 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
05-Feb-2024 15:34:09.644 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
05-Feb-2024 15:34:09.807 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
05-Feb-2024 15:34:09.808 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.86-dev]
05-Feb-2024 15:34:10.046 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-37409"]
05-Feb-2024 15:34:10.212 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 15:34:10.224 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-37409"]
05-Feb-2024 15:34:10.227 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
05-Feb-2024 15:34:10.228 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-37409"]
05-Feb-2024 15:34:10.236 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-37409"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.397 sec