Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.455 sec
------------- Standard Error -----------------
04-Dec-2024 20:30:20.840 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
04-Dec-2024 20:30:21.668 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
04-Dec-2024 20:30:21.826 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
04-Dec-2024 20:30:21.829 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.34-dev]
04-Dec-2024 20:30:21.935 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-38575"]
04-Dec-2024 20:30:22.127 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.
04-Dec-2024 20:30:22.133 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-38575"]
04-Dec-2024 20:30:22.135 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
04-Dec-2024 20:30:22.135 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-38575"]
04-Dec-2024 20:30:22.137 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-38575"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 1.405 sec