You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/12/08 12:22:01 UTC
[jira] Created: (JCR-2836) Unclosed threads in Jackrabbit
Unclosed threads in Jackrabbit
------------------------------
Key: JCR-2836
URL: https://issues.apache.org/jira/browse/JCR-2836
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Reporter: Jukka Zitting
Assignee: Jukka Zitting
The Tomcat integration test added in JCR-2831 shows the following warnings about Jackrabbit threads that remain in place even after the repository has been closed:
08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [DynamicPooledExecutor] but has failed to stop it. This is very likely to create a memory leak.
08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
It would be best to close all such background threads even if they are singleton daemon threads and thus unlikely to cause trouble when left unattended.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2836) Unclosed threads in Jackrabbit
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2836:
-------------------------------
Affects Version/s: 2.2.0
Fix Version/s: (was: 2.3.0)
2.2.1
In revision 1055117 I also fixed some Tomcat warnings about uncleared thread-local variables created by the PerQueryCache class, most likely due to the way it was being used from the IOCounters class.
All changes merged to the 2.2 branch in revisions 1055123 and 1055124.
> Unclosed threads in Jackrabbit
> ------------------------------
>
> Key: JCR-2836
> URL: https://issues.apache.org/jira/browse/JCR-2836
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.2.0
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 2.2.1
>
>
> The Tomcat integration test added in JCR-2831 shows the following warnings about Jackrabbit threads that remain in place even after the repository has been closed:
> 08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
> 08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [] appears to have started a thread named [DynamicPooledExecutor] but has failed to stop it. This is very likely to create a memory leak.
> 08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
> It would be best to close all such background threads even if they are singleton daemon threads and thus unlikely to cause trouble when left unattended.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2836) Unclosed threads in Jackrabbit
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2836.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
Fixed in revisions 1055068, 1055070 and 1055071.
> Unclosed threads in Jackrabbit
> ------------------------------
>
> Key: JCR-2836
> URL: https://issues.apache.org/jira/browse/JCR-2836
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 2.3.0
>
>
> The Tomcat integration test added in JCR-2831 shows the following warnings about Jackrabbit threads that remain in place even after the repository has been closed:
> 08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
> 08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [] appears to have started a thread named [DynamicPooledExecutor] but has failed to stop it. This is very likely to create a memory leak.
> 08-Dec-2010 12:14:58 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
> SEVERE: The web application [] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.
> It would be best to close all such background threads even if they are singleton daemon threads and thus unlikely to cause trouble when left unattended.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.