Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.548 sec
------------- Standard Error -----------------
07-Feb-2024 00:40:46.837 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
07-Feb-2024 00:40:48.043 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
07-Feb-2024 00:40:48.293 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
07-Feb-2024 00:40:48.293 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/8.5.99-dev]
07-Feb-2024 00:40:48.588 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33003"]
07-Feb-2024 00:40:48.867 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.
07-Feb-2024 00:40:48.893 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33003"]
07-Feb-2024 00:40:48.901 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
07-Feb-2024 00:40:48.902 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33003"]
07-Feb-2024 00:40:48.905 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-33003"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.444 sec