[
https://issues.apache.org/jira/browse/JS2-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854949#action_12854949
]
Ate Douma commented on JS2-1183:
--------------------------------
Example log output:
INFO: Stopping service Catalina
Apr 8, 2010 3:03:15 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-2] but
has failed to stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesStopTimerThread
SEVERE: A web application appears to have started a TimerThread named [Timer-1]
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 cancelled.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-6] but
has failed to stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named
[PageManagerNodeReapingThread] but has failed to stop it. This is very likely
to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named
[PortletApplicationManager Descriptor Change Monitor Thread] but has failed to
stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named
[Autodeployment File Scanner Thread] but has failed to stop it. This is very
likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [Thread-7] but
has failed to stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named
[PageManagerNodeReapingThread] but has failed to stop it. This is very likely
to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [WORKER_1] but
has failed to stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [WORKER_2] but
has failed to stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [WORKER_3] but
has failed to stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [WORKER_4] but
has failed to stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: A web application appears to have started a thread named [WORKER_5] but
has failed to stop it. This is very likely to create a memory leak.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearThreadLocalMap
SEVERE: A web application created a ThreadLocal with key of type
[java.lang.ThreadLocal] (value [java.lang.threadlo...@1cbf844]) and a value of
type [org.apache.cxf.bus.CXFBusImpl] (value
[org.apache.cxf.bus.cxfbusi...@1876d4]) but failed to remove it when the web
application was stopped. To prevent a memory leak, the ThreadLocal has been
forcibly removed.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearThreadLocalMap
SEVERE: A web application created a ThreadLocal with key of type
[javolution.context.Context$1] (value [javolution.context.contex...@217825])
and a value of type [javolution.context.HeapContext] (value
[javolution.context.heapcont...@156e1ed]) but failed to remove it when the web
application was stopped. To prevent a memory leak, the ThreadLocal has been
forcibly removed.
Apr 8, 2010 3:03:16 PM org.apache.catalina.loader.WebappClassLoader
clearThreadLocalMap
SEVERE: A web application created a ThreadLocal with key of type
[java.lang.ThreadLocal] (value [java.lang.threadlo...@107012c]) and a value of
type [org.apache.velocity.tools.view.context.ChainedContext] (value
[org.apache.velocity.tools.view.context.chainedcont...@de0ae6]) but failed to
remove it when the web application was stopped. To prevent a memory leak, the
ThreadLocal has been forcibly removed.
Apr 8, 2010 3:03:17 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
> Tomcat 6.0.24+ logs SEVERE errors on the console during shutdown from
> WebappClassLoader clearReferencesThreads and clearThreadLocalMap
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JS2-1183
> URL: https://issues.apache.org/jira/browse/JS2-1183
> Project: Jetspeed 2
> Issue Type: Task
> Components: Container
> Affects Versions: 2.2.1
> Reporter: Ate Douma
> Fix For: 2.2.2
>
>
> Since Tomcat 6.0.24 and higher Tomcat now actively verifies potential
> "shutdown" problems concerning application created thread, ThreadLocal
> instances etc.
> If it encounters such issues, it reports this as SEVERE errors, which by
> default end up in the console output or catalina.out.
> While these reporting "issues" indeed need looking into, the Console logging
> is rather annoying.
> For the Jetspeed 2.2.1 installer which will bundle Tomcat 6.0.26, I'll add an
> override of the Tomcat logging.properties to redirect these errors to the
> localhost FileHandler instead (logs/localhost.{date}.log).
> For Jetspeed 2.2.2 the reported "issues" warrant further investigation to see
> if these need to be solved or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
