Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.741 sec
------------- Standard Error -----------------
15-Mar-2024 20:45:54.554 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
15-Mar-2024 20:45:55.917 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
15-Mar-2024 20:45:56.125 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
15-Mar-2024 20:45:56.126 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/11.0.0-M19-dev]
15-Mar-2024 20:45:56.400 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-38483"]
15-Mar-2024 20:45:56.740 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 20:45:56.765 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-38483"]
15-Mar-2024 20:45:56.767 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
15-Mar-2024 20:45:56.778 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-38483"]
15-Mar-2024 20:45:56.780 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-38483"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.621 sec