Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.636 sec
------------- Standard Error -----------------
07-Mar-2024 18:19:20.283 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
07-Mar-2024 18:19:21.786 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
07-Mar-2024 18:19:21.977 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
07-Mar-2024 18:19:21.990 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/11.0.0-M18-dev]
07-Mar-2024 18:19:22.204 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42545"]
07-Mar-2024 18:19:22.374 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.
07-Mar-2024 18:19:22.407 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42545"]
07-Mar-2024 18:19:22.414 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
07-Mar-2024 18:19:22.415 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42545"]
07-Mar-2024 18:19:22.417 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42545"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.529 sec