[
https://issues.jboss.org/browse/ISPN-2786?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2786:
------------------------------------
[~galderz], the {{ThreadLocal.remove()}} documentation says that it only "Removes the
current thread's value for this thread-local variable." So if the thread-local
was accessed from multiple threads (e.g. because it's used in a webapp and each HTTP
request is handled by a different thread), calling {{ThreadLocal.remove()}} will *not*
remove all the instances of the thread local.
ThreadLocal memory leak in Tomcat
---------------------------------
Key: ISPN-2786
URL:
https://issues.jboss.org/browse/ISPN-2786
Project: Infinispan
Issue Type: Bug
Components: Marshalling, Transactions
Affects Versions: 5.1.8.Final
Reporter: Johann Burkard
Assignee: Galder ZamarreƱo
Labels: leak, local, memory, thread, threadlocal
Fix For: 5.3.0.Final
Just started an app using Infinispan 5.1.8.Final on Tomcat and got a few ThreadLocal
problems during un-deployment:
(Shortened)
{code}
key=org.jboss.marshalling.UTFUtils.BytesHolder
value=org.jboss.marshalling.UTFUtils$BytesHolder@697a1686
key=java.lang.ThreadLocal@36ed5ba6
value=org.infinispan.context.SingleKeyNonTxInvocationContext{flags=null}
key=org.infinispan.marshall.jboss.AbstractJBossMarshaller$1
value=org.infinispan.marshall.jboss.AbstractJBossMarshaller$1@75f10df7
value=org.infinispan.marshall.jboss.AbstractJBossMarshaller.PerThreadInstanceHolder
{code}
I do call {{DefaultCacheManager#shutdown()}} during un-deployment. :)
Thanks
--
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