I'm getting a little closer, should be closer sooner :)
The LocalTxInvocationContext that got left in thread local storage was
instantiated from here
http://pastie.org/1300157
That should bring me closer to the cause.
On Mon, 2010-11-15 at 10:29 -0500, Scott Marlow wrote:
Hi,
I'm trying to chase down some memory leaks for
https://jira.jboss.org/browse/JBAS-8613 (turned into a catch all jira
for a few different AS clustering failures).
I captured a picture of a classloader leak that is attached to
JBAS-8613.
The http thread threadLocals has a
org.infinispan.context.impl.LocalTxInvocationContext that is keeping the
classloader in memory (via what it references which is shown in the
abovce link or more directly
https://jira.jboss.org/secure/attachment/12338702/Eclipse+Memory
+Analyzer+Tool.png)
I'm looking at a different problem at the moment but would like to fix
this leak soon.
Why would org.infinispan.context.impl.LocalTxInvocationContext still be
referenced in thread local storage? Any suggestions on specific classes
that should be looked at?
Thanks,
Scott
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev