JDBCCacheLoader problem

[jorgemoralespou_2]

I have seen a strange behaviour in my app that I have traced down to the JDBCCacheLoader not working as I should have expected. Propably can be missused, so I post it here to see if anybody can help me.

I have a cache with a JDBCCacheLoader configured (JBC 1.4.1.SP8).
1- I put a new value in cache. New value is stored in DB.
2- I modify this object in cache, with same method (cache.put()) and the new value is not persisted in DB.

I have traced down through the code, and I see that ni JDBCCacheLoader ln:938 where it says:

 if(!override && oldNode != NULL_NODE_IN_ROW && attrs != null)
 {
 attrs.putAll(oldNode);
 }

My put is, I don't know how, calling this method with override set to false, so the original attribute map, is set to the attrs, overriding my new attributes, so they never get stored into database.

How can I call my put operation so override is true?

[mircea.markus]

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;
}

[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.

[mircea.markus]

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

[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.

[jorgemoralespou_2]

It seems that if I evict FQN.ROOT, only evicts nodes at primary level, and not its descendants.