Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.24 sec
------------- Standard Error -----------------
27-Nov-2024 11:51:21.103 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
27-Nov-2024 11:51:22.382 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
27-Nov-2024 11:51:22.584 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
27-Nov-2024 11:51:22.585 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.34-dev]
27-Nov-2024 11:51:22.756 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-44999"]
27-Nov-2024 11:51:22.986 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.
27-Nov-2024 11:51:22.999 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-44999"]
27-Nov-2024 11:51:23.006 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
27-Nov-2024 11:51:23.009 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-44999"]
27-Nov-2024 11:51:23.013 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-44999"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.129 sec