[JBoss JIRA] Created: (ISPN-316) Add aliasing capability to DefaultCacheManager
by Brian Stansberry (JIRA)
Add aliasing capability to DefaultCacheManager
----------------------------------------------
Key: ISPN-316
URL: https://jira.jboss.org/jira/browse/ISPN-316
Project: Infinispan
Issue Type: Feature Request
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: 4.1.0.CR1
The JBoss AS impl of the JBC CacheManager supports aliasing of cache configuration names. DefaultCacheManager can do the same. Helpful for preserving configuration compatibility across releases, e.g. an EJB3 bean class annotated with @CacheConfig(name="jboss.cache:service=EJB3SFSBClusteredCache") to work in AS 4.2 still works in AS 5 because I made "jboss.cache:service=EJB3SFSBClusteredCache" an alias for "sfsb-cache".
This doesn't affect the CacheManager API; it's an implementation detail; just inject a map of aliases and then resolve any unknown configuration names against it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (ISPN-673) Stopped cache still causing RPC timeouts on caller.
by Paul Ferraro (JIRA)
Stopped cache still causing RPC timeouts on caller.
---------------------------------------------------
Key: ISPN-673
URL: https://jira.jboss.org/browse/ISPN-673
Project: Infinispan
Issue Type: Bug
Components: RPC
Affects Versions: 4.2.0.ALPHA2
Reporter: Paul Ferraro
Assignee: Manik Surtani
Revision 2384 of org.infinispan.remoting.InboundInvocationHandlerImpl adds an 30 second wait loop for stopped caches, causing RPCs to timeout. For a stopped cache, GlobalComponentRegistry.getNamedComponentRegistry(...) returns null, since its global component registry entry is removed during ComponentRegistry.stop(), yet isDefined(...) will still return true. When not using strict peer to peer, this delay is inappropriate and causes the RPC to timeout.
--
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
14 years
[JBoss JIRA] Created: (ISPN-693) Be able to avoid querying the CacheStore when putting a new value
by Sanne Grinovero (JIRA)
Be able to avoid querying the CacheStore when putting a new value
-----------------------------------------------------------------
Key: ISPN-693
URL: https://jira.jboss.org/browse/ISPN-693
Project: Infinispan
Issue Type: Feature Request
Components: Loaders and Stores
Reporter: Sanne Grinovero
Assignee: Manik Surtani
Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
As mentioned on the mailing list, when doing
cache.withFlags(Flag.SKIP_REMOTE_LOOKUP).put( key, value )
this will cause a CacheLoaderInterceptor to try loading the data, there is no way to prevent this; this is a major performance issue when I'm not interested in the return value of put.
Apparently SKIP_REMOTE_LOOKUP work only to prevent return values from other nodes, but there's not way to prevent loading from the store. SKIP_CACHE_STORE would correctly skip the read, but I actually want the value to be written to the store, just needing to avoid the read.
--
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
14 years