Yes, this is a bug - thanks for reporting it. JBCACHE-1459
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199589#4199589
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199589
___
I started taking a look at this yesterday evening, I'll spend some time on it
Monday morning and post back.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199345#4199345
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=41
Anyone - any ideas as to what might be causing de-serialization problem?
Thank you.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199287#4199287
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199287
__
After come debugging here is what I see:
1. TCPServer does get request from the 'A' and send back non-empty map
(instance of Immutables.ImmutableMapWrapper) for the requested node.
2. TCPDelegatingCacheLoaders does get an empty Immutables.ImmutableMapWrapper
even though I see that it actually
