[jboss-dev-forums] [Design of JBossCache] - Re: Should users be notified of replication failures via a c

[bela@jboss.com]

Here's the use case:
- Node A and B
- A made a modification, sends the replication *asynchronously* to B. Can also be synchronous, just *no* TX
- B cannot apply it, e.g. because some other TX has locked the data
- The lock acquisition timeout on B kicks in and we don't apply the change on B
- A will have applied the change, but not B
- This is without TXs, or even with a TX but in async mode
- It would be good if we had a callback that was called on B if the replication could not be applied successfully.
- A cache exception does not work here, as the caller doesn't wait, and even if it did, we cannot throw an exception if we send the modification to B,C,D, and only B fails

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033181#4033181

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033181