Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.417 sec
------------- Standard Error -----------------
08-Apr-2024 08:40:31.185 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
08-Apr-2024 08:40:32.483 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"]
08-Apr-2024 08:40:32.550 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
08-Apr-2024 08:40:32.551 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.88-dev]
08-Apr-2024 08:40:32.898 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-46049"]
08-Apr-2024 08:40:33.085 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-Apr-2024 08:40:33.098 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-46049"]
08-Apr-2024 08:40:33.100 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
08-Apr-2024 08:40:33.101 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-46049"]
08-Apr-2024 08:40:33.114 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-46049"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.316 sec