Testsuite: org.apache.catalina.loader.TestWebappClassLoaderMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.535 sec
------------- Standard Error -----------------
28-Oct-2024 22:48:37.210 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
28-Oct-2024 22:48:38.753 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
28-Oct-2024 22:48:38.913 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
28-Oct-2024 22:48:38.914 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/11.0.1-dev]
28-Oct-2024 22:48:39.122 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-34133"]
28-Oct-2024 22:48:39.371 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.
28-Oct-2024 22:48:39.392 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-34133"]
28-Oct-2024 22:48:39.396 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
28-Oct-2024 22:48:39.397 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-34133"]
28-Oct-2024 22:48:39.401 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-34133"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 2.429 sec