I suppose it depends on how the feature is described, and the
specifics of the limitation.
My 2p: as you describe it, we should hesitate before advertising 2PC.
-Adrian Cole
On Sat, Apr 4, 2009 at 5:16 PM, Mircea Markus <mircea.markus(a)jboss.com> wrote:
Hi,
Current implementation of tx in JBC/infinispan might result in heuristic
transactions: e.g. if the coordinator cannot send an commit message (2nd
phase from 2PC) within a given timeout to some of the participants, this
might results in data being committed on some nodes and rollbacked on other.
Even worse, there is no way to take action and recover from the failure.
Would it make sense to have tx failure recovery mechanism in infinispan? I'm
referring here to something similar to the way DBs work, i.e. based on an
persistent tx logs, external notifications etc? Even though I didn't see any
such request on forums, I guess such a feature is mandatory for certain
systems, e.g. a financial application. Wdyt?
Cheers,
Mircea
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev