Adrian Crum wrote: > Oops, found more: > > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [TTLObject(0) pulse] but has failed to stop it. This is very > likely to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [TTLObject(1) pulse] but has failed to stop it. This is very > likely to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [ReferenceCleaner] but has failed to stop it. This is very > likely to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [ThreadPool-0] but has failed to stop it. This is very likely > to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [ThreadPool-1] but has failed to stop it. This is very likely > to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [ThreadPool-2] but has failed to stop it. This is very likely > to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [ThreadPool-3] but has failed to stop it. This is very likely > to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [TTLObject(async-update)-0] but has failed to stop it. This is > very likely to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [TTLObject(async-update)-1] but has failed to stop it. This is > very likely to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [TTLObject(async-update)-2] but has failed to stop it. This is > very likely to create a memory leak. > 2010-06-12 10:28:39,093 (OFBiz_Shutdown_Hook) [ > WebappClassLoader.java:1998:ERROR] A web application appears to have started > a thread named [TTLObject(async-update)-3] but has failed to stop it. This is > very likely to create a memory leak. > > > --- On Sat, 6/12/10, Adrian Crum <[email protected]> wrote: >> Latest trunk, during shutdown... >> >> 2010-06-12 10:28:39,000 (OFBiz_Shutdown_Hook) [ >> WebappClassLoader.java:1998:ERROR] A web application appears >> to have started a thread named [ExecutionPoolPulseWorker(0)] >> but has failed to stop it. This is very likely to create a >> memory leak. >> 2010-06-12 10:28:39,000 (OFBiz_Shutdown_Hook) [ >> WebappClassLoader.java:1998:ERROR] A web application appears >> to have started a thread named [ExecutionPoolPulseWorker(1)] >> but has failed to stop it. This is very likely to create a >> memory leak.
None of these are leaks; they are purely background threads, that are used to support non-blocking updates of various things. I believe they have the daemon bit set; I'll check on that. If they do, however, then the above messages are the bug.
