[JBoss JIRA] Updated: (ISPN-19) different cache manager impl : LocalCacheManager and ClusteredCacheManager
by Manik Surtani (JIRA)
[ https://issues.jboss.org/browse/ISPN-19?page=com.atlassian.jira.plugin.sy... ]
Manik Surtani updated ISPN-19:
------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.0.0.BETA1)
(was: 5.0.0.Final)
> different cache manager impl : LocalCacheManager and ClusteredCacheManager
> --------------------------------------------------------------------------
>
> Key: ISPN-19
> URL: https://issues.jboss.org/browse/ISPN-19
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core API
> Reporter: Mircea Markus
> Assignee: Manik Surtani
> Fix For: 6.0.0.Final
>
>
> consider having two CacheManagers impl: LocalCacheaManager and ClusteredCacheManager.
> This is in order to offer a more clear API to the user, who might want to use a specific cache manager.
> Currently, this is achieved through usage of GlobalConfiguration.getClusterDefault()/getNonClusterDefault(), but this is not very clear to the user.
> Also, after trying to create an replicated cache on a cache manager build on an "getNonClusterDefault" config, there will be an unclear error message:
> ""Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.horizon.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:129)
> ... 35 more
> Caused by: java.lang.NullPointerException
> at org.horizon.statetransfer.StateTransferManagerImpl.start(StateTransferManagerImpl.java:116)
> ... 40 more
> Error should be more specific, something like: "You're not allowed to deploy an clustered cache on an local cache manager".
> public void testCreateReplicatedCacheOnLocalCM() {
> GlobalConfiguration globalConfiguration = GlobalConfiguration.getNonClusteredDefault();
> globalConfiguration.setAllowDuplicateDomains(true);
> CacheManager dcm1 = new DefaultCacheManager(globalConfiguration);
> CacheManager dcm2 = new DefaultCacheManager(globalConfiguration);
> Configuration conf = new Configuration();
> conf.setCacheMode(Configuration.CacheMode.REPL_SYNC);
> dcm1.defineCache("replicated", conf);
> dcm2.defineCache("replicated", conf);
> dcm1.getCache("replicated");
> dcm2.getCache("replicated");
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (ISPN-748) provide an API to expose core operations omitting return values as safe alternative to Flags
by Sanne Grinovero (JIRA)
provide an API to expose core operations omitting return values as safe alternative to Flags
--------------------------------------------------------------------------------------------
Key: ISPN-748
URL: https://jira.jboss.org/browse/ISPN-748
Project: Infinispan
Issue Type: Feature Request
Components: Core API
Reporter: Sanne Grinovero
Assignee: Manik Surtani
Priority: Minor
Fix For: 5.0.0.BETA1, 5.0.0.Final
On mailing list we discussed the possibility to provide the same methods as defined by Map but omitting return values.
This would be useful for those cases in which return values are not needed, so that Infinispan can enable all possible optimizations to disregard retrieveing an appropriate return value.
Several alternatives where proposed, and there's also an interesting proposal to do the same relating to async methods, and the combination of async+noReturn
A suggestion:
cache.noReturnValue().remote(K); //returns void and enables both flags SKIP_CACHE_LOAD and SKIP_REMOTE_LOOKUP.
The advantage is that people refactoring code don't have to remember to adjust flags according to using the return value or not, or would at least get a compiler error in case of abuse of method; also Infinispan might introduce more optimizations in future and apply them without code changes for new flags arising.
See all discussion started by: http://lists.jboss.org/pipermail/infinispan-dev/2010-October/006484.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (ISPN-833) Revisit cache name predefinition limitation for cache servers
by Galder Zamarreño (JIRA)
Revisit cache name predefinition limitation for cache servers
-------------------------------------------------------------
Key: ISPN-833
URL: https://issues.jboss.org/browse/ISPN-833
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.0.0.BETA1, 5.0.0.Final
There're are two primary reasons why Infinispan servers require predefined caches to be started up on startup, and do not allow invocations to undefined caches:
1. Concurrent cache startups were resulting in NPEs (ISPN-635) - This is already solved since the 4.2.x days.
2. Infinispan has issues dealing with asymmetric clusters (ISPN-658).
Once these two issues have been resolved, revisit the limitation.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months