Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.526 sec
------------- Standard Error -----------------
01-May-2024 18:00:28.524 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
01-May-2024 18:00:30.035 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
01-May-2024 18:00:30.109 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
01-May-2024 18:00:30.110 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.89-dev]
01-May-2024 18:00:30.244 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42015"]
01-May-2024 18:00:30.517 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.
01-May-2024 18:00:30.528 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42015"]
01-May-2024 18:00:30.533 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
01-May-2024 18:00:30.534 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42015"]
01-May-2024 18:00:30.547 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-42015"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.419 sec