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: 0.981 sec
------------- Standard Output ---------------
class java.lang.Thread [pool-1-thread-1] EXITING
class java.lang.Thread [pool-1-thread-5] EXITING
class java.lang.Thread [pool-1-thread-2] EXITING
class java.lang.Thread [pool-1-thread-3] EXITING
class java.lang.Thread [pool-1-thread-4] EXITING
------------- ---------------- ---------------
------------- Standard Error -----------------
16-Aug-2017 10:15:30.473 INFO [main] org.apache.catalina.startup.LoggingBaseTest.setUp Starting test case [testTimerThreadLeak]
16-Aug-2017 10:15:30.842 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio2-127.0.0.1-auto-1"]
16-Aug-2017 10:15:30.864 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Tomcat]
16-Aug-2017 10:15:30.864 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/9.0.0.M27-dev
16-Aug-2017 10:15:31.018 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio2-127.0.0.1-auto-1-35063"]
16-Aug-2017 10:15:31.201 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)
16-Aug-2017 10:15:31.203 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:
16-Aug-2017 10:15:31.206 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio2-127.0.0.1-auto-1-35063"]
16-Aug-2017 10:15:31.257 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Tomcat]
16-Aug-2017 10:15:31.259 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio2-127.0.0.1-auto-1-35063"]
16-Aug-2017 10:15:31.260 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio2-127.0.0.1-auto-1-35063"]
------------- ---------------- ---------------

Testcase: testTimerThreadLeak took 0.965 sec

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

Last Updated: Wed, 16 Aug 2017 06:00:05 ().Python Logo