Ok - so if you go synch, the JTA transaction commits, after which if you're using REPL_SYNCH, the cache state is replicated across the cluster in a 'TreeCache' transaction. If you go asynch, the replication happens asynchronously with respect to the thread the JTA transaction occurs on.
Are the replication transaction semantics the same for both REPL_SYNCH and REPL_ASYNCH? The docs seem to imply that the cache contents could be inconsistent across cache members if error occur when REPL_ASYNCH is used. Finally, if an error occurs in the replication, and REPL_SYNCH is used, is an exception thrown? Is there a recommended error strategy, like evicting the data modified in the transaction since it is inconsistent with the resource manager? I assume any exception thrown does not affect the outcome of the JTA transactions as it has been committed prior to replication... Thanks again for the replies - this is very helpful. /doug View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878598#3878598 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878598 ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
