Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.945 sec
------------- Standard Error -----------------
01-Jan-2024 10:30:23.578 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
01-Jan-2024 10:30:25.289 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"]
01-Jan-2024 10:30:25.347 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
01-Jan-2024 10:30:25.362 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/11.0.0-M16-dev]
01-Jan-2024 10:30:25.574 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-41089"]
01-Jan-2024 10:30:25.842 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.
01-Jan-2024 10:30:25.858 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-41089"]
01-Jan-2024 10:30:25.864 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
01-Jan-2024 10:30:25.865 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-41089"]
01-Jan-2024 10:30:25.875 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-41089"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.768 sec