[JBoss JIRA] Created: (ISPN-1384) Remote processes can access cache before it's started
by Michal Linhard (JIRA)
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: Manik Surtani
version:
Infinispan 5.1.0-SNAPSHOT last commit fc94449eec33469057614a13cbfe59e4f4e855fd Author: Michal Linhard <michal(a)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
13 years, 3 months
[JBoss JIRA] Created: (ISPN-1324) On-demand startup of Caches from InboundInvocationHandlerImpl
by Galder Zamarreño (JIRA)
On-demand startup of Caches from InboundInvocationHandlerImpl
-------------------------------------------------------------
Key: ISPN-1324
URL: https://issues.jboss.org/browse/ISPN-1324
Project: Infinispan
Issue Type: Feature Request
Reporter: Galder Zamarreño
Assignee: Manik Surtani
Fix For: 6.0.0.FINAL
Allow InboundInvocationHandlerImpl to start caches on demand when requests for a particular cache are received.
Things to consider are:
- How to deal with programmatically created caches. There's always a chance that a cache might not have been defined when the cache request is received in a node. If programmatically defined caches were sent around the cluster (as suggested by Randal in ISPN-1147), this might not be such a problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (ISPN-1104) Upgrade to Scala 2.9.0.final
by Trustin Lee (JIRA)
Upgrade to Scala 2.9.0.final
----------------------------
Key: ISPN-1104
URL: https://issues.jboss.org/browse/ISPN-1104
Project: Infinispan
Issue Type: Task
Reporter: Trustin Lee
Assignee: Trustin Lee
Priority: Trivial
Fix For: 5.0.0.FINAL, 5.0.0.CR3
Scala 2.9.0.final has been released with various bug fixes and improvements. It's backward compatible as long as the code is recompiled, so I assume it's safe to upgrade and we should upgrade because people will be using Scala 2.9 when 5.0.0.Final is out.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months