Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.605 sec
------------- Standard Error -----------------
10-Jan-2024 06:11:02.285 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
10-Jan-2024 06:11:03.844 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"]
10-Jan-2024 06:11:03.919 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
10-Jan-2024 06:11:03.920 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/11.0.0-M17-dev]
10-Jan-2024 06:11:04.146 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-42659"]
10-Jan-2024 06:11:04.329 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.
10-Jan-2024 06:11:04.335 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-42659"]
10-Jan-2024 06:11:04.343 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
10-Jan-2024 06:11:04.345 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-42659"]
10-Jan-2024 06:11:04.364 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-42659"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.501 sec