[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1384) Remote processes can access cache before it's started

[Michal Linhard (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628773#comment-12628773 ] 

Michal Linhard commented on ISPN-1384:
--------------------------------------

It's the same as in JBPAPP-7173 : http://www.qa.jboss.com/~mlinhard/run21.zip

> Remote processes can access cache before it's started
> -----------------------------------------------------
>
>                 Key: ISPN-1384
>                 URL: https://issues.jboss.org/browse/ISPN-1384
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.0.1.FINAL
>            Reporter: Michal Linhard
>            Assignee: Galder Zamarreño
>             Fix For: 5.1.0.ALPHA2 , 5.1.0.FINAL
>
>         Attachments: edg-thread-problem.zip
>
>
> version:
> Infinispan 5.1.0-SNAPSHOT last commit fc94449eec33469057614a13cbfe59e4f4e855fd Author: Michal Linhard <michal at linhard.sk> Date:   Wed Sep 7 13:42:32 2011 +0200
> The mechanism that locks cache while it is being created and started is not in effect when accessing the cache remotely.
> The problem happens in this scenario:
> 1. Thread1 does DefaultCacheManager.getCache and starts the cache to the point where ComponentRegistry for that cache exists, but the cache is not yet started
> 2. Thread2 (originating in JGroups layer) does call via InboundInvocationHandlerImpl and gets hold of the ComponentRegistry for the cache and calls perform() on the command
> (note that the Thread2 doesn't obtain the cache via DefaultCacheManager.getCache and therefore it doesn't have to wait on the cacheCreateLock or CacheWrapper lock)
> the problem manifests itself in JBPAPP-7173 where using unstarted CacheLoaderInterceptor leads to NPE.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira