[infinispan-issues] [JBoss JIRA] (ISPN-1764) Remove threadLocal in org.infinispan.context.AbstractInvocationContextContainer

Dan Berindei (JIRA) issues at jboss.org
Thu May 29 17:45:16 EDT 2014


     [ https://issues.jboss.org/browse/ISPN-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei resolved ISPN-1764.
--------------------------------

    Fix Version/s: 7.0.0.Alpha1
                   6.0.1.Final
       Resolution: Done


The {{AbstractInvocationContextContainer}} class has been removed with the ISPN-3777 fix. A thread-local is still used in {{InvocationContextContainerImpl}}, but only if a classloader was specified with {{AdvancedCache.with(ClassLoader)}}.

> Remove threadLocal in org.infinispan.context.AbstractInvocationContextContainer
> -------------------------------------------------------------------------------
>
>                 Key: ISPN-1764
>                 URL: https://issues.jboss.org/browse/ISPN-1764
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Core
>            Reporter: Sanne Grinovero
>            Assignee: Dan Berindei
>             Fix For: 7.0.0.Alpha1, 6.0.1.Final
>
>
> The javadocs in org.infinispan.context.AbstractInvocationContextContainer mention:
> {quote}// See ISPN-1397.  There is no real need to store the InvocationContext in a thread local at all, since it is passed
>    // as a parameter to any component that requires it - except for two components at the moment that require reading
>    // the InvocationContext from a thread local.  These two are the ClusterCacheLoader and the JBossMarshaller.  The
>    // former can be fixed once the CacheStore SPI is changed to accept an InvocationContext (see ISPN-1416) and the
>    // latter can be fixed once the CacheManager architecture is changed to be associated with a ClassLoader per
>    // CacheManager (see ISPN-1413), after which this thread local can be removed and the getInvocationContext() method
>    // can also be removed.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


More information about the infinispan-issues mailing list