Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.042 sec
------------- Standard Error -----------------
15-Mar-2024 15:33:13.622 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
15-Mar-2024 15:33:15.218 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
15-Mar-2024 15:33:15.386 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
15-Mar-2024 15:33:15.386 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/11.0.0-M19-dev]
15-Mar-2024 15:33:15.643 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-35085"]
15-Mar-2024 15:33:15.868 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.
15-Mar-2024 15:33:15.877 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-35085"]
15-Mar-2024 15:33:15.879 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
15-Mar-2024 15:33:15.880 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-35085"]
15-Mar-2024 15:33:15.885 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-35085"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.814 sec