-
1. Re: Replicated cache TimeoutException
galder.zamarreno Sep 8, 2010 9:54 AM (in response to feci)1 of 1 people found this helpfulAre all 3 nodes receiving the same messages? If they are and all 3 nodes try to modify the same key, you'll get lock issues like this cos all nodes would be trying to modify the same key at the same time. Not sure what the key represents in your case, but if the key is associated with the JMS message, then it'd better if only one of the nodes consumed the message and stored in Infinispan.
-
2. Re: Replicated cache TimeoutException
feci Sep 9, 2010 8:35 AM (in response to galder.zamarreno)yes, I made it that way, I'm asking if node is a coordinator and only coordinator is putting messages...
How is the remove method working? Can there be a problem, if the three nodes are removing the same key? Let say I want to take the message from the cache (all three nodes in same time), with remove, but I want that only one node will suceed, other two will get null...
-
3. Re: Replicated cache TimeoutException
galder.zamarreno Sep 16, 2010 12:38 PM (in response to feci)1 of 1 people found this helpfulpublic void testEmptySecondLevelCacheEntry() throws Exception {getSessions().getCache().evictEntityRegion(Item.class.getName());Statistics stats = getSessions().getStatistics();stats.clear();SecondLevelCacheStatistics statistics = stats.getSecondLevelCacheStatistics(Item.class.getName() + ".items");Map cacheEntries = statistics.getEntries();assertEquals(0, cacheEntries.size());} -
4. Re: Replicated cache TimeoutException
feci Sep 16, 2010 5:56 PM (in response to galder.zamarreno)The problem is, that I'm getting that kind of exception even when I'm starting new node. I'm putting to cache only from one node, but when I start another node, it throws again
org.infinispan.util.concurrent.TimeoutException: Replication timeout for ...
How can I put something to synchronously replicated cache even during new nodes are starting? I gues they are retrieving the states and so on, so it locks the cache...
-
5. Re: Replicated cache TimeoutException
galder.zamarreno Sep 23, 2010 1:13 PM (in response to feci)Hmmm, where is that TimeoutException being reported? On the node doing the put? Or the node starting up?
I doubt it's the node joining since it's not in a state that accepts invocations if it's doing state transfer. The node serving the state shouldn't be locking either since it does a non-blocking state transfer which basically reads the cache and this does not block. So, I wonder where this repl timeout comes from exactly. If you could be provide a unit test replication this it would be of a lot of help.