[jboss-dev-forums] [Design of JBossCache] - Re: Classloader leak via CacheImpl.invocationContextContaine

jason.greene@jboss.com do-not-reply at jboss.com
Thu Jun 7 17:41:39 EDT 2007


Ah yes. Perhaps just clearing it is better. Although then it wouldn't survive calls.


  | cache.getInvocationContext().getOptionOverrides().setCacheModelLocal(true);
  | cache.put(fqn, key, value);
  | cache.put(fqn, key, value);
  | 

Another option would be to have CacheImpl store a strong reference to every known context, which would go away on cleanup, although this would probably be expensive (at least for creation of the context)

Last, we could require that calling code hold the reference (somewhat cryptic, but this is an advanced feature). 


  | InvocationContext ic = cache.getInvocationContext();
  | ic.getOptionOverrides().setCacheModelLocal(true);
  | cache.put(fqn, key, value);
  | cache.put(fqn, key, value);
  | 

-Jason

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052332#4052332

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052332



More information about the jboss-dev-forums mailing list