Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.145 sec
------------- Standard Error -----------------
20-Nov-2024 13:43:25.731 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
20-Nov-2024 13:43:26.904 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
20-Nov-2024 13:43:27.110 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
20-Nov-2024 13:43:27.110 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.34-dev]
20-Nov-2024 13:43:27.341 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33893"]
20-Nov-2024 13:43:27.565 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.
20-Nov-2024 13:43:27.607 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33893"]
20-Nov-2024 13:43:27.610 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
20-Nov-2024 13:43:27.612 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33893"]
20-Nov-2024 13:43:27.614 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33893"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.069 sec