Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.736 sec
------------- Standard Error -----------------
25-Jan-2024 18:06:32.296 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
25-Jan-2024 18:06:33.795 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
25-Jan-2024 18:06:34.013 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
25-Jan-2024 18:06:34.013 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/11.0.0-M17-dev]
25-Jan-2024 18:06:34.249 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41869"]
25-Jan-2024 18:06:34.459 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.
25-Jan-2024 18:06:34.468 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41869"]
25-Jan-2024 18:06:34.470 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
25-Jan-2024 18:06:34.471 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41869"]
25-Jan-2024 18:06:34.473 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-41869"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.604 sec