This content has been marked as final. Show 1 reply
what configuration are you using?
What's strange is, after a while, the specific cache that got removed and recreated by the monitor program could not be read or replicated anymore, even though the traces clearly showed the entry did get added to the cache instance on N2
so the put on N3 does get replicated on N2 but N1 cannot read it from N2? Are you sure that you do any operation on N3 *after* it joined the cluster? After creating the cache it will take a time until cluster is discovered and joined. I suggest logging cluster membership (cache.getMembers()) before doing any operations on N3. Also make sure that the number of members N3 sees is the one desired(i.e. 3), before doing any work with it.