Log in to follow, share, and participate in this community.
Thread Should users be notified of replication failures via a call
Should users be notified of replication failures via a callThis thread is for JBCACHE-1015. My opinion is that cluttering up the listener is not how I would ideally like to do this - I'd prefer to throw a CacheException as it is an exceptional circumstance.
Removal policiesTalking with some fellow devs, I'd like to have the eviction policies really handle removes not just evicts. One use case is: 1. I am only allowed to fetch a user's profile once every 4 hours. 2. I must remove this p...
InvocationContext in JBCMethodCall?Minor food for thought... While responding to a user forum question (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104915) it occurred to me that other interceptor-based architectures I see include...
Distributed lock managerReferencing this thread and various other discussions. Is the subject something we want to implement in JBoss Cache in some shape or form, at some stage? I agree that here are scalability issues with such a feature,...
Thread WARN message if tx is not ACTIVE or PREPARING
WARN message if tx is not ACTIVE or PREPARINGCacheImpl.getCurrentTransaction() logs a WARN if it finds a tx associated with the thread that isn't ACTIVE or PREPARING. Found at least one use case where this isn't valid. If a user does some sort of bulk update op...
Thread org.jboss.cache.lock.TimeoutException in write / read intens
org.jboss.cache.lock.TimeoutException in write / read intensHi there, Trying my luck with JBossCache 1.4.1.SP1 on a Websphere 6.1.0.3 cluster with 2 nodes each node with 1 server. The OS on both machines is Windows XP Professional SP2. I'm using the replSync-service.xml c...
Thread CacheListener events for state transfer marshalling
CacheListener events for state transfer marshallingThere's no CacheListener event generated before a node is about to be marshalled for state transfer. Use case for this is EJB3 SFSB, where we are storing a bean context in the cache. EJB3 spec says we should invoke a...
JBCACHE-957 Discussion ThreadDiscussions related to http://jira.jboss.com/jira/browse/JBCACHE-957 -- Allow per-node configuration of LockParentForChildInsertRemove. Elias Ross had a good suggestion on this: The Node itself keeps a NodeLock in...
TxInterceptor logging of exceptionsTxInterceptor catches all exceptions that come up from lower in the interceptor chain, logs them at INFO, and then rethrows the exception if there isn't a failSilently option set. 1) Why log at all if the exception i...
Last minute 2.0 API suggestions1. Have Node.removeChild() return true if the node was removed 2. Add a Node.size() or Node.dataSize() to count basically getData().size(). The problem (in terms of efficiency) is that getData() makes a copy. 3. Node....
Cache.removeRegion(Fqn)We need to expose removeRegion(Fqn) in Cache. Right now you can create a region but there is no way to clean it up without doing ((CacheSPI) cache).getRegionManager().removeRegion(Fqn);
JBCACHE-941 discussionhttp://jira.jboss.com/jira/browse/JBCACHE-941 From the issue: The java.util.Collections utility class supplies useful methods for dealing with legacy interfaces and wrapping collection classes for concurrency, type ...
markNodeCurrentlyInUse() - race conditionIt seems to me that Region#markNodeCurrentlyInUse() does not really do what it is supposed to do. Basically, it adds an event to the queue. And what can happen is that 4 seconds later (say, if event queue processing ...
SELECT FOR UPDATE semanticsI know I raised this issue somewhere before, but can't find it, so here we go again... We're about to finalize the 2.x API; before we do, can we add something that provides semantics similar to SELECT FOR UPDATE, i.e...
PojoCache uses a special node factoryQuick brain dump... I think PojoCache has some issue with its _JBossInternal_ node(s) -- things like data versioning changes with optimistic locking, potential lock contention due to the large number of child nodes, ...
Thread Last chance for any changes to the 2.0.0 API
Last chance for any changes to the 2.0.0 APIGuys, I hope to cut an ALPHA2 of JBC 2.0.0 soon. After this, I want to freeze the API so there are no more changes to it during beta/cr releases, so let's get this right. The original API I proposed is on this wiki ...
Serialization Compatibility TestsThis is a discussion about http://jira.jboss.com/jira/browse/JBQA-536. I'd like to give some background for JBC developers to catch up on what we are trying to do. We would like to ensure backwards compatibility of ...
Buddy state transferCurrently, in HEAD branch, it seems that each buddy collects its own state and then sends it across the wire to his buddies in RPC call. Should we change this approach so that upon receipt of buddy reconfiguration me...
Thread JBCACHE-890 - idea for consolidating meta-data on a node
JBCACHE-890 - idea for consolidating meta-data on a nodeI think the JIRA issue and the API 2.0 covers most of the issue. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994779 What would be some example "flags" to eventually introduce? Data security, mu...