You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2013/06/25 11:02:20 UTC
[jira] [Resolved] (SANTUARIO-359) Possible memory leak when using
Thread Pool
[ https://issues.apache.org/jira/browse/SANTUARIO-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved SANTUARIO-359.
-------------------------------------------
Resolution: Duplicate
This is already fixed in 1.5.4.
Colm.
> Possible memory leak when using Thread Pool
> -------------------------------------------
>
> Key: SANTUARIO-359
> URL: https://issues.apache.org/jira/browse/SANTUARIO-359
> Project: Santuario
> Issue Type: Bug
> Components: Java
> Affects Versions: Java 1.5.2
> Environment: Windows Server 2008 x64, Tomcat 7.0.40, Java 1.6.0_43
> Reporter: Vyacheslav Mayorov
> Assignee: Colm O hEigeartaigh
> Labels: memory-leak, tomcat
>
> Tomcat warns about possible memory leak:
> Jun 18, 2013 2:17:00 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
> SEVERE: The web application [/] created a ThreadLocal with key of type [org.apache.xml.security.utils.UnsyncByteArrayOutputStream$1] (value [org.apache.xml.security.utils.UnsyncByteArrayOutputStream$1@4d586d6a]) and a value of type [byte[]] (value [[B@687771d1]) 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira