Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.478 sec ------------- Standard Error ----------------- 08-Feb-2024 10:32:31.905 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak] 08-Feb-2024 10:32:33.233 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"] 08-Feb-2024 10:32:33.377 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat] 08-Feb-2024 10:32:33.377 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/11.0.0-M17-dev] 08-Feb-2024 10:32:33.579 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-45997"] 08-Feb-2024 10:32:33.820 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. 08-Feb-2024 10:32:33.829 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-45997"] 08-Feb-2024 10:32:33.835 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat] 08-Feb-2024 10:32:33.837 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-45997"] 08-Feb-2024 10:32:33.845 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-45997"] ------------- ---------------- --------------- Testcase: testTimerThreadLeak took 2.373 sec