Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.332 sec
------------- Standard Error -----------------
19-Dec-2024 18:37:09.334 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
19-Dec-2024 18:37:10.046 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"]
19-Dec-2024 18:37:10.098 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
19-Dec-2024 18:37:10.104 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.35-dev]
19-Dec-2024 18:37:10.246 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-41675"]
19-Dec-2024 18:37:10.416 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.
19-Dec-2024 18:37:10.424 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-41675"]
19-Dec-2024 18:37:10.426 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
19-Dec-2024 18:37:10.427 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-41675"]
19-Dec-2024 18:37:10.431 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-41675"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 1.245 sec