Run| Workspace| Log| Issues| Fixes| Pre-reqs| Stats| XRef| Maven Repository Proxy Log Gump Logo

Details

File Contents

Testsuite: org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.171 sec
------------- Standard Output ---------------
class java.lang.Thread [pool-1-thread-3] EXITING
class java.lang.Thread [pool-1-thread-2] EXITING
class java.lang.Thread [pool-1-thread-5] EXITING
class java.lang.Thread [pool-1-thread-1] EXITING
class java.lang.Thread [pool-1-thread-4] EXITING
------------- ---------------- ---------------
------------- Standard Error -----------------
22-Jun-2018 01:56:09.259 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
22-Jun-2018 01:56:09.810 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
22-Jun-2018 01:56:09.887 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Tomcat
22-Jun-2018 01:56:09.888 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.53-dev
22-Jun-2018 01:56:10.005 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36256"]
22-Jun-2018 01:56:10.190 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.lang.Thread.sleep(Native Method)
 org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:119)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)
22-Jun-2018 01:56:10.202 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [pool-1-thread-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.lang.Thread.sleep(Native Method)
 org.apache.catalina.loader.TestWebappClassLoaderExecutorMemoryLeak$ExecutorServlet$Task.run(TestWebappClassLoaderExecutorMemoryLeak.java:119)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 java.lang.Thread.run(Thread.java:748)
22-Jun-2018 01:56:10.227 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36256"]
22-Jun-2018 01:56:10.278 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service Tomcat
22-Jun-2018 01:56:10.279 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36256"]
22-Jun-2018 01:56:10.280 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-36256"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 1.147 sec

Apache Gump, Gump, Apache, the Apache feather logo, and the Apache Gump project logos are trademarks of The Apache Software Foundation.

Last Updated: Fri, 22 Jun 2018 00:00:06 ().Python Logo