| Run | | | Workspace | | | Log | | | Issues | | | Fixes | | | Pre-reqs | | | Stats | | | XRef | | | Maven Repository Proxy Log | |
||
Testsuite: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.678 sec ------------- Standard Output --------------- class java.lang.Thread [pool-1-thread-4] EXITING class java.lang.Thread [pool-1-thread-2] EXITING class java.lang.Thread [pool-1-thread-1] EXITING class java.lang.Thread [pool-1-thread-3] EXITING class java.lang.Thread [pool-1-thread-5] EXITING ------------- ---------------- --------------- ------------- Standard Error ----------------- 02-Jan-2025 10:30:06.640 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak] 02-Jan-2025 10:30:08.182 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"] 02-Jan-2025 10:30:08.282 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat] 02-Jan-2025 10:30:08.283 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/12.0.0-M1-dev] 02-Jan-2025 10:30:08.529 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-38789"] 02-Jan-2025 10:30:08.833 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-1-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.base/java.lang.Thread.sleepNanos0(Native Method) java.base/java.lang.Thread.sleepNanos(Thread.java:496) java.base/java.lang.Thread.sleep(Thread.java:527) org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:120) java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) java.base/java.lang.Thread.run(Thread.java:1575) 02-Jan-2025 10:30:08.852 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-1-thread-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.base/java.lang.Thread.sleepNanos0(Native Method) java.base/java.lang.Thread.sleepNanos(Thread.java:496) java.base/java.lang.Thread.sleep(Thread.java:527) org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:120) java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) java.base/java.lang.Thread.run(Thread.java:1575) 02-Jan-2025 10:30:08.875 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-38789"] 02-Jan-2025 10:30:08.884 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat] 02-Jan-2025 10:30:08.887 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-38789"] 02-Jan-2025 10:30:08.898 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-38789"] ------------- ---------------- --------------- Testcase: testTimerThreadLeak took 2.55 sec
Apache Gump, Gump, Apache, the Apache feather logo, and the Apache Gump project logos are trademarks of The Apache Software Foundation.
Last Updated: Thu, 02 Jan 2025 06:00:03 ().