-
1. Re: JDBCCacheLoader problem
mircea.markus Jul 4, 2008 7:06 AM (in response to jorgemoralespou_2)thanks for spotting this.
This is a bug, indeed.
I've created http://jira.jboss.com/jira/browse/JBCACHE-1384
It is good that override is false at that point (that means that we do not want to *replace* the existing value). The problem is that overriding logic is broken, the old values override the new ones.
Here is my fix:if(!override && oldNode != NULL_NODE_IN_ROW && attrs != null)
{
Map newOne = new HashMap(oldNode);
if(attrs != null) newOne.putAll(attrs);
attrs = newOne;
} -
2. Re: JDBCCacheLoader problem
jorgemoralespou_2 Aug 17, 2008 1:28 PM (in response to jorgemoralespou_2)Is there an easy way to save all in-memory state to Database. I need to update database state, since it may be corrupt, prior to updating my running instances with a patched version of JDBCCacheLoader with the fix you suggested?
Any help will be appreciated. -
3. Re: JDBCCacheLoader problem
mircea.markus Aug 18, 2008 9:13 AM (in response to jorgemoralespou_2)an idea would be to have a small program that
a) starts a new cluster instance which would fetch all in memory state
b) this instance uses passivation
c) call cache.evict after state retrieval finished
d) exit -
4. Re: JDBCCacheLoader problem
jorgemoralespou_2 Aug 18, 2008 10:16 AM (in response to jorgemoralespou_2)I was already working on it, although I didn't thought on passivation, rather in a cache.put for every node. I'll try cache.evict, as it seems rather easier.
-
5. Re: JDBCCacheLoader problem
jorgemoralespou_2 Aug 18, 2008 12:38 PM (in response to jorgemoralespou_2)It seems that if I evict FQN.ROOT, only evicts nodes at primary level, and not its descendants.