You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2016/11/03 11:45:58 UTC
[jira] [Updated] (ISIS-1531) Possible memory leak
[ https://issues.apache.org/jira/browse/ISIS-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated ISIS-1531:
----------------------------------
Summary: Possible memory leak (was: Possible memory link)
> Possible memory leak
> --------------------
>
> Key: ISIS-1531
> URL: https://issues.apache.org/jira/browse/ISIS-1531
> Project: Isis
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.13.1
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: 1.18.0
>
>
> [The stacktrace below is old, from an earlier version. Still think there are issues though]
> Jan 07, 2013 5:25:58 PM org.apache.catalina.core.StandardContext startInternal
> SEVERE: Error filterStart
> Jan 07, 2013 5:25:58 PM org.apache.catalina.core.StandardContext startInternal
> SEVERE: Context [/app-webapp-0.0.1-SNAPSHOT] startup failed due to previous errors
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [com.google.inject.internal.util.$Finalizer] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] appears to have started a thread named [DefaultQuartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak.
> Jan 07, 2013 5:25:58 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
> SEVERE: The web application [/app-webapp-0.0.1-SNAPSHOT] created a ThreadLocal with key of type [com.google.inject.internal.InjectorImpl$1] (value [com.google.inject.internal.InjectorImpl$1@54ea55f0]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@64b02b1d]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)