Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.885 sec
------------- Standard Error -----------------
04-Feb-2024 17:08:28.612 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
04-Feb-2024 17:08:29.469 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
04-Feb-2024 17:08:29.588 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
04-Feb-2024 17:08:29.589 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/10.1.19-dev]
04-Feb-2024 17:08:29.831 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36713"]
04-Feb-2024 17:08:29.983 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-Feb-2024 17:08:29.991 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36713"]
04-Feb-2024 17:08:30.001 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
04-Feb-2024 17:08:30.002 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36713"]
04-Feb-2024 17:08:30.005 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36713"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 1.791 sec