"norbert" wrote : Try this with synchronous replication to see whether there are any 'CacheException' when 'put' ist called right before retriving 'null'. | | (Asynchronous Replication will catch these Exceptions internally since they do not occur synchronous to the corresponding method-call). |
An interesting idea (and I will try it to see what happens), but in my case, the put in question is happening in another VM. Furthermore, I know that the replication is working because before (and after) the null occurrance, get invocations for the same key are working. Could there be a "hidden" exception in the get invocation that your suggestion might expose? Since I am not using transactions, I am not sure what that would be. I am only using SERIALIZABLE as an isolation level because it seemed to fix an unrelated issue where a cache node existed, but its corresponding object did not (yet). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3856460#3856460 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3856460 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
